automationgame.com

Hey guys, quick question, when is a "save" triggered in the game, is it after every change, X amount of time or when you switch tabs? I have a car made that absolutely refuses to save the fact that it has a forged crank and H beam rods, each time I quit then re-load the car it has cast/cast. I have tried many things short of starting over and have not found a way to get it to "save" my changes. This happens with other things as well and it is trial and error (AKA "save", quit, reload) to see if a change is saved. Basically I just want to know of a sure fire way to force the game to save so I know my file(s) are correct.

Pretty sure it's after each change, so I'm not sure why yours is reverting all of the time. Whenever I quit, even right after I make a change, it's still saved.

Indeed it should save after every single change you make, if it doesn't and you don't have the hold button pressed, that's a bug.
Can you send us the car that shows this behavior so that we can take a look?

Let me take a guess, the autosave function makes Automation "resource hungry" on 720p and better resolution. I had several crashes due to luna and memory erros. I mean it keeps Automation busy, right?

No, the saving is not an issue in this, the live updating of all stats more so. Still, you should not get lua errors. Which version are you on and what errors do you get?

It is version 150502 .

This is a crash due to some sorta memory access failure:

Name der fehlerhaften Anwendung: Automation Launcher.exe, Version: 1.0.0.0, Zeitstempel: 0x55125ee1
Name des fehlerhaften Moduls: Automation_Shipping_SA.dll, Version: 0.0.0.0, Zeitstempel: 0x55436064
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0004b690
ID des fehlerhaften Prozesses: 0x%9
Startzeit der fehlerhaften Anwendung: 0x%10
Pfad der fehlerhaften Anwendung: %11
Pfad des fehlerhaften Moduls: %12
Berichtskennung: %13

Fehlerbucket , Typ 0
Ereignisname: APPCRASH
Antwort: Nicht verfügbar
CAB-Datei-ID: 0

Problemsignatur:
P1: Automation Launcher.exe
P2: 1.0.0.0
P3: 55125ee1
P4: Automation_Shipping_SA.dll
P5: 0.0.0.0
P6: 55436064
P7: c0000005
P8: 0004b690
P9:
P10:

This might be one of the lua errors:

Angefügte Dateien:
C:\Users\christian\AppData\Local\Temp\WER7C42.tmp.WERInternalMetadata.xml

Diese Dateien befinden sich möglicherweise hier:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_Automation Launc_4ddc1aea416590bf6ba74f485d9f77bb5b70939d_0d6582b8

Analysesymbol:
Es wird erneut nach einer Lösung gesucht: 0
Berichts-ID: 4a807c40-f7c2-11e4-8046-6cf0499e1223
Berichtstatus: 1

So when does that happen?

I have a similar bug to this, when I exit out of the game it crashes with two report to Windows boxes, then when I check the car I was working on all the files have reverted to the first pass settings.

What I mean by first pass is the settings I initially use, e.g compression 6:1, cam at 100, 8k redline etc then I tune the engine. When this bug happens the engine and trim files have reset to those initial settings

The crash on exit is known and not critical in any way, that's due to a small memory leak in the graph drawing used in the car designer.

I can't recreate the problem you are having with the engine not saving, can you upload the car & engine so that we can have a look? (Also steps to reproduce the bug)

Randomly. The game uses about 50% of the physical memory.

@OP: please have a look at this thread, it should answer the original question, viewtopic.php?p=72477#p72477

@chrisbo28: that is not anything common, not seen it before except in the case of turbo loading / unloading. Otherwise it can be two things: a corrupt game install (try installing it again) or a faulty computer (which I sure don't hope is the case).

If the later was the case it would happen all the time but the system runs pretty stable otherwise. I run 4GB DDR2-800 Ram and Windows 7 Ultimate 64bit.

I am finding this problem to be very random and it isn't based on the exit crash (as you said) because I had the crash and my file was fine. The only thing I can remember is that it happened on cars that I did a lot of fine-tuning and moving between screens. When I do a quick car I haven't had issues (so far, lol).