V1 Virtual Display (Valentine One) - Page 8

f1racr · January 17th, 2010, 04:37 PM

I don't think it really needs a skin change really........ what Dejan has done is fine for the moment.

What's most important is the sounds so that the car PC will alert the driver when signals are detected..... it's the best and fastest way to alert. Then next most important is to bring up the display, then 3rd is how it looks.

That would be my priority levels.

MattJackson86 · January 17th, 2010, 04:38 PM

I would agree. I think the look of the interface doesn't matter yet as long as the plugin works.

_Dejan_ · January 17th, 2010, 07:01 PM

Quote:

Originally Posted by MattJackson86

Any updates on this? Are we still waiting on the skin tool to be complete before this plugin can be released?

Thanks,
Matt

Hi Matt,

Last two week's has been for me realy busy and Im not do anything for any of my plugins... Im writing application for my job (cca. 10-16h per day) so after that Im not have any interest to programm something for me or continue with plugins

Lite version of this app will be used in GPSTrack plugin as standalone application to monitor where is your car, see tracks, see saved POI...

I have working skin tool but as we found is not very good to use CF pictures in this application for updating every time when data came to comport. it start lagging and using too much CPU power resources... I have one idea and I think I will start working on it wednesday when I will go to job(and not programming all day at home) and send it to fraser to test performance. If not be good I will use your drawing for LED's...

Quote:

Originally Posted by MattJackson86

I would agree. I think the look of the interface doesn't matter yet as long as the plugin works.

Yes Im not very good with photoshop but with basic skill I will try make it look's best as possible... With skin we will spend more time when will be finished because there can be some changes...

MattJackson86 · January 18th, 2010, 01:34 AM

Thanks for the update Dejan. Sorry you have been so busy at work. Thats no fun

I understand though. Hopefully we can get the plugin functioning without the skin tool as that seems to be causing slowness issues and we can work on the look of the plugin later.

I have attached the audio for a Ka alert. This was edited from the one Fraser provided and this only contains 1 beep. It is 200 milliseconds long and we will have to figure out how much gap to leave between each beep to signify the signal strength. Something like 700 milliseonds for a strength 1, 600 for strength 2, 500 for 3, etc. This way a strength 8 has 0 gap. I played around with this and it sounds close to the real thing, but without recording a sample of these real alerts we wont be able to get exact. Fraser if you can provide any other sound samples that would be great. x, K, Laser, J out, etc. I dont know if you can code these pauses into the app or if you will need 8 audio files each with a pause in them?

- Matt

f1racr · January 30th, 2010, 05:00 PM

Sorry there hasn't been any updates for a while. Dejan and I have been trying to sort out the display and not having 100% CPU. This seems to have been related to a Flux module which is now available and in the Beta we are both running it seems to be working well

Now I think we'll focus on just adding the sounds and having it auto appear and the first release version should be available.

Sorry for the wait, but trust me, as it was, it made your PC unusable...4-5 seconds to respond to button presses etc so now it seems a million percent better.

Dejan is a great developer and is working very hard for us all ! Please be patient and please donate if you do end up using the plugin and appreciate it.

MattJackson86 · January 30th, 2010, 07:47 PM

Great new Fraser. Thanks for working so hard on this with Dejan and getting it developed/tested. Glad you got the slowness issue sorted out and im looking forward to the first version being released. Good Job once again Dejan.

MattJackson86 · February 11th, 2010, 02:21 PM

Fraser, whats the latest? I saw you posted some info and a picture a while back but it seems to have disappeared.

f1racr · February 11th, 2010, 10:19 PM

Yeah sorry, I was reminded that my screenshot was off CF 3.1 so didn't really want to post pictures of the new interface before official release in case it wasn't good form.

I'll cut up the picture a little maybe to remove the interface and just leave the working plugin shot maybe..........

It's all working perfectly. Dejan has solved the slow update issue and my V1 has been picking up K and Ka band as expected and showing good signal strength.

Only real changes before it's usable is for Dejan to add audible alerts which I think is next on the list, but he hasn't been able to do that for a couple of weeks..... not sure what his timeframe is for that, but I don't think it's usable till then as watching the display for things to change isn't safe motoring !

Even having auto display I think isn't important relative to having audible alerts.........

I know he'll get there...... I'm just the testing geek, I just do what I can ...... wish I could help out with writing the code too, but I'm not that much of a geek I'm afraid !!

LOL

MattJackson86 · February 11th, 2010, 10:25 PM

Are we in need of any more audio recordings?

f1racr · February 11th, 2010, 10:29 PM

Well ideally we should have one of K, X and Laser bands as well, but the reality is that for the first version of the plugin any old noise will do that's distinctive....... as it's only really there to bring the drivers attention to the fact there's a radar source close.