Exiting Driver Issue

Seemingly a problem somewhere in the session, goodness knows what. Deleted said session..revamped, loaded driver and exited driver...no problem.
Gremlins maybe!!!!

Issue solved, I think.
 
I have the same problem valbridge. Not as frequent as you. Except I am not as polite referring to it as a "close". It is a crash in my book.
 
I've had that occur after very long periods of driving, but I could never track down to exactly what caused the crash. It could be anything that's causing the problem including bad content, or a faulty script somewhere in that particular route. The only way to find out is to create a clean route and drive that, or drive another unrelated route and see if it occurs with that one. If it doesn't then there's something wrong with the route or session that's causing the crash.
 
OK this is now happening on a regular basis in TRS19. Each time I exit from a driver session the program closes [crashes]. This is a recent development which I have noticed over the past few days. Prior to that all worked ok. I do not get the same issue when exiting driver in T:ANE so I doubt it is a PC problem. Perhaps I have a bug in TRS19 which no-one else appears to have!
Quite frankly its bloody infuriating. Bug report maybe?

EDIT.....Did load and run one of the pre-loaded routes and exiting driver with no problem...Now I am thinking maybe it has something to do with the route I am creating or maybe an asset within it. Geez, completely at a loss here.
 
Last edited:
Try a database repair and see if that fixes the problem. This is over and above the automatic one that runs after a crash. If a QDR doesn't work, try an Extended DBR. You do that by pressing the CTRL key while clicking on Repair Database.
 
Try a database repair and see if that fixes the problem. This is over and above the automatic one that runs after a crash. If a QDR doesn't work, try an Extended DBR. You do that by pressing the CTRL key while clicking on Repair Database.

Thanks John,
First I knew of an extended DB repair. So have actioned same. We will see if this fixes the issue. I have noticed quite a bit of payware from Auroran and not sure if I should disable these assets or leave them if they are standard to TRS19. Maybe you could advise. Now I will construct a test session and see if I still get a comp crash.
 
Thanks John,
First I knew of an extended DB repair. So have actioned same. We will see if this fixes the issue. I have noticed quite a bit of payware from Auroran and not sure if I should disable these assets or leave them if they are standard to TRS19. Maybe you could advise. Now I will construct a test session and see if I still get a comp crash.

I wouldn't touch the payware as that's most likely the built-in stuff.

I hope the repair worked.
 
I wouldn't touch the payware as that's most likely the built-in stuff.

I hope the repair worked.

So good so far. Perhaps that was all that was required, a deeper db repair...fingers x'd. I was almost at the point of trashing TRS19.
Thanks John.
 
So good so far. Perhaps that was all that was required, a deeper db repair...fingers x'd. I was almost at the point of trashing TRS19.
Thanks John.

Hm, I ask myself how can I initiate a deeper db repair? Didn't find it in any TRS19-menu. Did you manage this via console?

_______
Josef
 
Thanks. But I can't find any 'repair database' in my TRS19 installation (build: 98592)
Maybe you mean 'Rebuild Database' in the developer menu instead?

Yes.

Open the developer menu.

press the CTRL-key at the same time you click on 'Rebuild Database'.
 
Back
Top