Bugs in 2.0.1

Is Virtual Radar Server not behaving itself? If so then please report it here.
agw
Posts: 2248
Joined: Fri Feb 17, 2012 3:20 am

Re: Bugs in 2.0.1

Post by agw » Wed Feb 26, 2014 12:59 am

IE7 and 8 definitely won't work, the new site needs a modern browser. I'm a little surprised that IE9 doesn't work, I'll have to install that somewhere and see what's happening on there. IE10+ and the latest versions of Chrome & Firefox will work.

737mech
Posts: 12
Joined: Tue Feb 25, 2014 9:14 pm

Re: Bugs in 2.0.1

Post by 737mech » Wed Feb 26, 2014 1:52 am

Ok working fine in google chrome, thank you!

Sentry_e3
Posts: 81
Joined: Wed May 15, 2013 11:57 pm

Re: Bugs in 2.0.1

Post by Sentry_e3 » Wed Feb 26, 2014 8:22 pm

Don't know if it's a bug, but after the update the new version is displayed in local (127.0. Etc..) but not on internet (still the old version displayed). Clearing the browser cache changes nothing :(

agw
Posts: 2248
Joined: Fri Feb 17, 2012 3:20 am

Re: Bugs in 2.0.1

Post by agw » Thu Feb 27, 2014 12:11 am

I'm guessing that you had a bookmark on the local version? If you change from GoogleMap.htm to desktop.html then you should see the new site.

jfm
Posts: 82
Joined: Thu May 10, 2012 4:09 pm

Re: Bugs in 2.0.1

Post by jfm » Sun Mar 09, 2014 8:56 pm

Hi Andrew, I've found a couple of possible bugs. I don't seem them on the bug tracker.

1. When viewing the callsign report for an aircraft that I know was broadcasting positions, there is no path shown on the map. Previously it used to show a line from the first to last position (not sure if it's ever worked since version 2 was released).

2. When entering the IP address of a receiver, I accidentally put two "." (something like 192.168..100.50). This caused an exception.

3. I'm running via Mono on OSX. I happened to see this error in the console log: "mono[660]: WARNING: CFSTR("Copyright \37777777702\37777777651 2010 onwards, Andrew Whewell") has non-7 bit chars, interpreting using MacOS Roman encoding for now, but this will change. Please eliminate usages of non-7 bit chars (including escaped characters above \177 octal) in CFSTR()."

Thanks!

agw
Posts: 2248
Joined: Fri Feb 17, 2012 3:20 am

Re: Bugs in 2.0.1

Post by agw » Wed Mar 12, 2014 9:44 pm

jfm wrote:there is no path shown on the map
Reports do show the path on the map, but there needs to be a first and last latitude & longitude on the database for it to display. If you're using BaseStation or the Database Writer plugin then they don't get written to the database until roughly 25 minutes after the final message is received from the aircraft. If you're not seeing them for flights that were last seen more than 25 minutes ago then let me know.
jfm wrote:I accidentally put two "." (something like 192.168..100.50). This caused an exception.
Thanks for letting me know, I've put it on the list :)
jfm wrote:I'm running via Mono on OSX. I happened to see this error in the console log
Yes, I noticed this a while back, I think it's always said it. From what I recall it's complaining about the © symbol in the copyright message in a resource file. There's nothing wrong with putting copyright symbols in copyright messages, Microsoft stick them in there by default if you create the project under Visual Studio. I imagine that it's one of the libraries that Mono is using that's moaning about it, other flavours of Linux don't show the message. I didn't do anything about it because firstly I want the © in there and secondly if they did drop the high bit at some point in the future it's only going to affect the text on the Help | About screen. It's untidy but it should be benign.

jfm
Posts: 82
Joined: Thu May 10, 2012 4:09 pm

Re: Bugs in 2.0.1

Post by jfm » Thu Mar 13, 2014 2:23 pm

agw wrote:
jfm wrote:there is no path shown on the map
Reports do show the path on the map, but there needs to be a first and last latitude & longitude on the database for it to display. If you're using BaseStation or the Database Writer plugin then they don't get written to the database until roughly 25 minutes after the final message is received from the aircraft. If you're not seeing them for flights that were last seen more than 25 minutes ago then let me know.
I checked flights from days ago and the map pans to the general area of the flight, but the path is not displayed. I can check the DB to confirm that first and last position is recorded.

I also saw this error in the Chrome developer console. Not sure if it's related.

(27) Uncaught ReferenceError: MarkerWithLabel is not defined
bundle-68efedcf-fcdf-4b76-9968-c938f6502f35.js:80

oh-bomm
Posts: 6
Joined: Sun Oct 27, 2013 6:15 pm
Location: EFKK

Re: Bugs in 2.0.1

Post by oh-bomm » Fri Mar 14, 2014 9:00 am

Hi

Read that VRS 2.0.1 so i tried to look on it but everything else wen't great but not when i wanted to look at options then I got this message i Ubuntu 13. Operatingsystem with mono.
message.jpg
Screenshot
message.jpg (153.04 KiB) Viewed 3530 times
***********************************************************************
You learn everyday something new

jfm
Posts: 82
Joined: Thu May 10, 2012 4:09 pm

Re: Bugs in 2.0.1

Post by jfm » Sun Mar 16, 2014 6:35 pm

jfm wrote:I checked flights from days ago and the map pans to the general area of the flight, but the path is not displayed. I can check the DB to confirm that first and last position is recorded
I confirmed that flights with first/last lat/lon in the DB are not showing a path on the map.

agw
Posts: 2248
Joined: Fri Feb 17, 2012 3:20 am

Re: Bugs in 2.0.1

Post by agw » Sun Mar 16, 2014 7:29 pm

jfm wrote:I also saw this error in the Chrome developer console. Not sure if it's related.

(27) Uncaught ReferenceError: MarkerWithLabel is not defined
bundle-68efedcf-fcdf-4b76-9968-c938f6502f35.js:80
Yes, that would cause problems :) However I'm not able to reproduce this. Are you running under Mono or Windows? Could you switch bundling off (Tools | Options | Web Site, set Enable bundling to No), reproduce the error and let me know what it says in the console please?

Locked