Route Viewer for Openbve

Ciao a Tutti!!!
I have a small problem with the "Route Viewer" (V. 1.4.0.0): every 5 or 6 updates with the f5 key, the program crashes. Does anyone has the same problem and knows possibile solutions?
Thank you very much for interest

Hi, i did comment on this a while back, i dont think the problem has been resolved, try loading "memchecker", watch what happens when you run route viewer, the program does not seem to dump the memory used when pressing F5, as soon as its used your graphics memory it crashes, I tend nowadays to restart route viewer after 4 or 5 refreshes...regards

I think some people have found that they had older versions of .net and updating increased performance. However the it still wont address the reasons that this can happen, as it is due to the way the route viewer allocates memory when loading routes and the way .net's garbage collection system works. It is possible to edit the programme to call the garbage collector during reloads, but this is a crude hack really.

Intresting I can`t get Ver V. 1.4.0.0 to work at all get a missing DLL in the microsoft error page but it wont tell me the missing DLL now using the older version any ideas

I'm having problems with v1.2 of the ObenBVE RouteViewer. If I load even just a basic route, it lags to hell, and then when I quit even after just a few seconds of use, my whole PC lags, everything I try to use takes an age meaning I have to restart the PC

Dysonsphere wrote:Intresting I can`t get Ver V. 1.4.0.0 to work at all get a missing DLL in the microsoft error page but it wont tell me the missing DLL now using the older version any ideas

Just to be a checker, Make sure that your Routeviewer is not separate from your Openbve folder. Everything must be placed into that directory for it to work. If that isn't the case, try reinstalling the dependencies.

Hope this helps :-)

2. It is better to have the same version of openBVE and Routeviewer - it is known openBVE 1.2 + RouteViewer 1.4 does not do any good

Ah thx Dexter that is probably the reason.

Hi,

It is almost certain a memory issue. Yesterday I got a warning about windows resizing the pagefile because of a low ammount of memory available. It happens I've got 4Gb RAM and a huge virtual RAM pagefie. I was making experiments on my test route and as a consequence, RouteViewer's F5 was used all the time. It seems closing and reopenning the program solves this, at least until a fixed version of RouteViewer is available.