CTD while turning back from track to main menu

BerScott

I'm experiencing a CTD with certain mod I'm working on. Not sure if it could be due to the 5.500 stringlines that my upgrades.ini has :p But it is full of Mass+=100, Inertia*=0.009 values that sometimes could be crossed depending on the upgrades, and I'm not sure if that could cause the problem.

This is what my Windows 7 Pro x64 says about it (sorry, my Win7 is in spanish):
Code: 
Firma con problemas:
  Nombre del evento de problema:	APPCRASH
  Nombre de la aplicación:	rFactor.exe
  Versión de la aplicación:	1.2.5.5
  Marca de tiempo de la aplicación:	4705a035
  Nombre del módulo con errores:	rFactor.exe
  Versión del módulo con errores:	1.2.5.5
  Marca de tiempo del módulo con errores:	4705a035
  Código de excepción:	c0000005
  Desplazamiento de excepción:	001ba118
  Versión del sistema operativo:	6.1.7601.2.1.0.256.48
  Id. de configuración regional:	3082
  Información adicional 1:	0a9e
  Información adicional 2:	0a9e372d3b4ad19135b953a78882e789
  Información adicional 3:	0a9e
  Información adicional 4:	0a9e372d3b4ad19135b953a78882e789
Pic related: http://i.imgur.com/PYgJoZz.png

Mention too that sometimes it has appear some info about ntdll.dll in other errors. Here is the error related:
Code: 
Firma con problemas:
  Nombre del evento de problema:	APPCRASH
  Nombre de la aplicación:	rFactor.exe
  Versión de la aplicación:	1.2.5.5
  Marca de tiempo de la aplicación:	4705a035
  Nombre del módulo con errores:	ntdll.dll
  Versión del módulo con errores:	6.1.7601.18247
  Marca de tiempo del módulo con errores:	521ea8e7
  Código de excepción:	c0000005
  Desplazamiento de excepción:	0002e3be
  Versión del sistema operativo:	6.1.7601.2.1.0.256.48
  Id. de configuración regional:	3082
  Información adicional 1:	0a9e
  Información adicional 2:	0a9e372d3b4ad19135b953a78882e789
  Información adicional 3:	0a9e
  Información adicional 4:	0a9e372d3b4ad19135b953a78882e789

Also these are some stringlines from my tracelog set out to =1000 that I think it could be related to the problem.
Code: 
slot.cpp      440: CollisionBodyChecksum=1113804395
vehload.cpp   429: +x force applied when moving in +x direction
vehload.cpp   434: -x force applied when moving in -x direction
vehload.cpp   990: RPM-torque brake > throttle @ 0.000000

Some random stringlines from upgrades.ini related to mass, inertia and other modifiers.
Code: 
    HDV=[GENERAL]
    HDV=Mass+=10.88
    HDV=Inertia*=(1.0100, 1.0188, 1.0482)
    HDV=CGRearRange+=(0.050, 0.005, 0)
    HDV=[FRONTLEFT]
    HDV=SpinInertia*=1.3029
    HDV=DamperMult*=0.888

I hope someone can, please, explain me why is this happening. If you need some additional info, please just ask.

Regards.
 
Last edited:
To be honest, i see entries like "HDV=Mass+=10.88" or "HDV=Inertia*=(1.0100, 1.0188, 1.0482)" the first time.
I'm talking about the "+" and "*".
And when different upgrades have same entries with different values, i don't think that this is helpful ;).

Do you have the same CTD when you use the mod without the ugrades.ini?
 
I'm still trying to find what is causing the CTD.

For now I've check it without the upgrades.ini, or at least removing all the stringlines which could be causing that, or all except which just made references to gmt upgrades.

Seems that make bakfire upgrades could be causing a CTD, but I've removed them and still is happening.

I've changed the shaders and still is happening.

So i'm in blank already.
 
Try it with a trace, to figure out what the reason is.

A trace is a possibility to find out what reason a crash has.
Here is what you have to do to create a trace-file:

- if you don't have one, create a shortcut from rfactor.exe
- rightclick on it an choose "properties"
- in the line "target" add this at the end: trace=30 ATTENTION, there has to be a space in front of the "trace".
- the new line at the end should look like ......rfactor.exe trace=30 or ......rfactor.exe" trace=30
- click OK and start the game with the shortcut
- move to the point where the game crashes
- when it crashed, go to your rfactor installation folder, and then into the folder UserData/LOG
- there you'll find a file called trace.txt
- open it, scroll to the end and look if there is something written what may have caused the crash.
- or maybe you find something strange in another line of the trace-file.
- to keep the file, rename it, because it will be overwritten when you next time start the game
 
BerScott said:
Also these are some stringlines from my tracelog set out to =1000 that I think it could be related to the problem.
Code: 
slot.cpp      440: CollisionBodyChecksum=1113804395
vehload.cpp   429: +x force applied when moving in +x direction
vehload.cpp   434: -x force applied when moving in -x direction
vehload.cpp   990: RPM-torque brake > throttle @ 0.000000
Click to expand...

Thanks anyway.
 
Sorry forgot that you've postet that before.

Did you make the trace with or without upgrades ?

And, how many cars are included in the mod?
 
With upgrades, of course. Anyway it seems to be the same without upgrades. Specifically it is a car I've made for a mod, the mod itself runs without no problems and I've done at least 10 cars for it.
 
Do you know which special car it is?

Or is it 1 of the 10?

Then i would suggest to remove all and put one after the other back in game to find out which one it is.
Otherwise it will be very difficult to find out the "crasher", i guess.
 
It is a specific car, that's why I'm talking about the upgrades.ini as a cause :rolleyes:
 
But when you've removed all upgrades from that car (deactivated the line to the upgrade.ini in the *.veh-file), and the crash still happens, it seems to be something wrong with that car itself. Don't you think too?
 
It is happening an interesting thing. When I make a change, like removing the backfire or changing the shaders, I run rFactor, go to track, back to menu and all seems to be ok. Then I close rFactor, I start it again, go on track, back to menu and CTD again!

The really strange thing is that it seems to happen totally randomly. It's a bit frustrating.
 
Sorry about the double post, but seems that I have a clue.

After having a talk with a friend of mine who is programmer, he says that it is possible that those "HDV=Inertia*=" lines that redapg commented is causing the problem. But not by the command itselfs, the problems seems to be that them is causing an overflow. In computer programing terms, that means that these parameters could be be causing that rFactor can't handle a large number returned by the "=*" modifiers. These days I will try to modify all the upgrades.ini and try if it works with a short value and see what happens.
I've confirmed that just removing the "=" symbol before the +/-/*, causing to rFactor stop the CTDing.

The interesting part is that I've removed completly these references yesterday and still was CTDing.
 
Last edited:
Really strange....

But go on with posting informations, i'm always interested in things that cause problems and the reason why they do it. :)
 
I've added another different CTD error related to a dll.

Right now I keep totally stuck about this. I've descarted shaders, the backfire upgrades and now I've discarted the physics strings related, I mean the modifiers I've posted early.

I've spent two weeks to find the cause of this and I'm starting to get really frustrated. Also seems that ISI developers don't have any word to write here, so what now? :(
 
Hard to say with only that few information.

You are the only one who knows what you have done....

Errors can have many reasons, caused by mod, track, game, system, other software running .....

It's a little bit like a quiz, to find out what the failure(s) cause, here over the forum.

It's the same as when i would ask here why my (real) car don't starts up when i turn the key. You know what i mean?

And that's why ISI don't posts here, i guess. Without having all files you use, it is almost impossible to say something helpful.

I would suggest to go back to the roots.

Make a fresh rFactor-light installation, and then put your mod into it, one car after the other.

Normally that is the easiest way to find out what reason strange behaviour has.

There must have been a point where the mod have run normal, right?
Maybe you can reconstruct that?

And...IMPORTANT... do ONLY ONE CHANGE and test then.
Otherwise it will be hard for yourself ;)

And, by the way, an update.ini with 5500 (?) lines in it..... do you really need that?
 
redapg, I appreciate your observation, but that few information I've provided is barely enought to make any developer confirm if is it possible to make crossed physic upgrades with these math symbols like *=, +=, etc. Also any dev could explain what could be causing the tracelog stringlines I've posted or even explain what could be related to the exception errors report.
Obviously I'm not asking for the final solution, but a bit of info related could make me discard some possibilities to find the cause by myself :).

I've done a huge upgrades.ini because I've add several GEN file strings related and I use 6 LODS for almost every part.
 
Well, after sometime without no solution seems that some users running my mod don't have issues while running Windows 8. I suspect that the issue could be caused by the ntdll.dll file as reported in the appcrash report pasted in the first post.

I hope that ISI devs could gift us with theire presence here :rolleyes:.
 
You must log in or register to reply here.

Back
Top