SPASKIS
Registered
It is quite common when making the first steps in modding, to get stuck because the track (or car) won't surpass the loading screen provoking rFactor 2 to crash without giving a clue about what could be casuing the crash.
In those cases it is important to have some type of methodology that helps locating the faulty item(s) which are causing the crash. In many of these cases, the only clue available is where in the loading screen the crash occurs.
For this reason I have created a loading screen which I hope could be useful for amateur modders. For sure track modders have it easier to implement it than car modders that would need to overwrite Joesville' loading track in dev mode or modify a track including it for single player mode.
I have myself located the marked events by introducing bugs on purpose that would cause a crash or simply provide an error message. In other words, I don't know in detail the exact loading sequence rF2 uses. I grant for sure that devs know better than me the exact loading sequence and where in the progress bar is represented each step.
Hence, I will be glad to be corrected or provided with more relevant information to further improve the loading screen. Feel free to make your comments...
In the image you can see how I introduced an "error causing flag" within the scn. If a crash would occur prior to appearing this message, it would mean that the faulty item is located before the "flag" I introduced. I hope it is clear enough. I thought this exmaple helps understanding the last paragraph of the image.
In those cases it is important to have some type of methodology that helps locating the faulty item(s) which are causing the crash. In many of these cases, the only clue available is where in the loading screen the crash occurs.
For this reason I have created a loading screen which I hope could be useful for amateur modders. For sure track modders have it easier to implement it than car modders that would need to overwrite Joesville' loading track in dev mode or modify a track including it for single player mode.
I have myself located the marked events by introducing bugs on purpose that would cause a crash or simply provide an error message. In other words, I don't know in detail the exact loading sequence rF2 uses. I grant for sure that devs know better than me the exact loading sequence and where in the progress bar is represented each step.
Hence, I will be glad to be corrected or provided with more relevant information to further improve the loading screen. Feel free to make your comments...
In the image you can see how I introduced an "error causing flag" within the scn. If a crash would occur prior to appearing this message, it would mean that the faulty item is located before the "flag" I introduced. I hope it is clear enough. I thought this exmaple helps understanding the last paragraph of the image.
Attachments
Last edited:
