In this German Forum is a discussion about a System.NullReferenceException during playing.
http://www.tssf.eu/f...p?topic=10334.0
The problem exist with several Routes and Activitys.
Now they have replaced the runactivity.exe in the actual experimental release by the same file from the SVN Repository and the Problem seems to be solved.
Can somebody who can reed German have a look on this discussion?
Page 1 of 1
System.NullReferenceException after playing
#2
Posted 31 March 2014 - 01:55 AM
If it's occurring during exit, it's a known issue (and occurs everywhere, *some* of the time) and can be ignored.
#3
Posted 31 March 2014 - 05:09 AM
Well, I took a quick look and just skimmed the text. From that I can tell, they´re NOT talking about the problem happening when exiting ORTS, but randomly throughout activities. Somebody mentioned, it could have to do with certain cab functions, yet this possible cause could not be confirmed.
Much of the conversation also is about reporting bugs, here or at Launchpad. It´s said, that somebody reported the bug, yet got a message it was a duplicated bug report.
There might be more, that I missed quickly skimming the conversation...
Cheers, Markus
Much of the conversation also is about reporting bugs, here or at Launchpad. It´s said, that somebody reported the bug, yet got a message it was a duplicated bug report.
There might be more, that I missed quickly skimming the conversation...
Cheers, Markus
#4
Posted 31 March 2014 - 05:24 AM
It's indeed not about the exit error.
It's about the error in the render function (RenderFrame.cs, lines 137 or 138 - invalid object or invalid comparison - could well be different 'versions' of same problem).
Regards,
Rob Roeterdink
It's about the error in the render function (RenderFrame.cs, lines 137 or 138 - invalid object or invalid comparison - could well be different 'versions' of same problem).
Regards,
Rob Roeterdink
#5
Posted 31 March 2014 - 05:46 AM
markus_GE, on 31 March 2014 - 05:09 AM, said:
Much of the conversation also is about reporting bugs, here or at Launchpad. It´s said, that somebody reported the bug, yet got a message it was a duplicated bug report.
If it got marked as a duplicate, that just means someone else already reported it. ;) Unless they disagree that the bugs are duplicates, in which case they can either unmark it themselves or comment to that effect. Bugs are definitely better than forum posts for tracking things, though.
#6
Posted 31 March 2014 - 06:56 PM
The Discussion about the duplicate Bug is a minor problem.
The most interesting thing is:
the german Community says:
The experimental Releases, produce the bug.
IF THEY REPLACE the runactivity.exe in the experimental releases by the same File (same release) from the SVN REPOSITORY
THEY DON'T HAVE ANY PROBLEM during playing.
This ( same???) files also don't have the same sizes!!!
There must be a difference between this two files runactivity.exe
hopefully you can detect the reason for that bug (duplicated or not) in this file-difference.
The most interesting thing is:
the german Community says:
The experimental Releases, produce the bug.
IF THEY REPLACE the runactivity.exe in the experimental releases by the same File (same release) from the SVN REPOSITORY
THEY DON'T HAVE ANY PROBLEM during playing.
This ( same???) files also don't have the same sizes!!!
There must be a difference between this two files runactivity.exe
hopefully you can detect the reason for that bug (duplicated or not) in this file-difference.
#7
Posted 01 April 2014 - 12:00 AM
eugenR, on 31 March 2014 - 06:56 PM, said:
IF THEY REPLACE the runactivity.exe in the experimental releases by the same File (same release) from the SVN REPOSITORY
THEY DON'T HAVE ANY PROBLEM during playing.
THEY DON'T HAVE ANY PROBLEM during playing.
They are compiled with different options (Subversion is "debug", unless people forget, and the public releases are all "release") so will have different performance characteristics and for odd timing bugs that may affect how reliably they occur. I do not believe for that the bug only exists in one version.
#8
Posted 01 April 2014 - 10:42 AM
Hi James,
thanks for your explication.
I understand.
To find an error, you have to use for testing the debug-Version, but the debug-Version don't produce this time critical error......
We hope you will find it once by hazard
thanks for your explication.
I understand.
To find an error, you have to use for testing the debug-Version, but the debug-Version don't produce this time critical error......
We hope you will find it once by hazard
Page 1 of 1