Steam version Failed to launch

[_Azza]

if it helps at all i'm getting the exact same issue

Well its kind of good to know I'm not the only one haha :/

Has the game engine changed much between the steam and non steam version? Because I could run the latest non-steam version fine.

[Disturbed2k14]

if it helps at all i'm getting the exact same issue

Well its kind of good to know I'm not the only one haha :/

Has the game engine changed much between the steam and non steam version? Because I could run the latest non-steam version fine.

there must be significant changes in the latest update, i was able to run it before as well

[zeussy]

arg my poor brain. I just realised that I have had this issue, before during development, and it was a real stickler to pin down.

Scratching my brain to try and remember what on earth it was.

[_Azza]

Keep thinking Zeussy! I'm counting on ya

I ran a RAM test that win7 has built in and it came back with no errors after restarting..

[zeussy]

So I talked this problem over on #lua but lost the logs. Talk to a friend and found the logs the final chat line was:

<caswal> I don't have time to figure this out, I'll revert all my changes that caused it.

Thanks past self. Working on a way to help debug this on the first small bug fix update.

[zeussy]

I do have a crazy theory, which is a foreign lua51.dll is being run instead of ours.

The crazy issue that I never managed to solve was the table length operator # in lua just broke and did not work.

If you delete the lua51.dll from the Automation folder, does it still Play?

[_Azza]

I do have a crazy theory, which is a foreign lua51.dll is being run instead of ours.

The crazy issue that I never managed to solve was the table length operator # in lua just broke and did not work.

If you delete the lua51.dll from the Automation folder, does it still Play?

Okay so I moved lua51.dll out of my automation folder, started the game I get the window open to select Options and Play game, click play game and it tells me it failed due to missing lua51.dll file.

Still not working after the latest patch. (I didn't assume it was for my benefit but thought id let you know)

Cheers for your help thus far, I hope we can nut it out soon.

[zeussy]

Alright, let's try and work this problem. 2 things to try:

Thing 1

Take this file:

scripts.zip

(1.48 KiB) Downloaded 317 times

And place the scripts folder in the zip into your automation folder. Make sure to not do the accidental extracting of having a folder called scripts made, with then the scripts folder in that. If that makes sense?

If correct it should be like this when you go into the scripts folder, and it's various sub folders:

ScriptsTest.PNG (119.49 KiB) Viewed 3946 times

If you start the game (Just double click on Automation_Shipping_Steam.exe)

It should say:

Init
Lua Version: "Lua 5.1"
LuaJIT 2.0.3

If that all works, we can then start more complex scripts and see if the problem is what I think it is.

Thing 2 (A possible work around)

Download this zip:

lua51.zip

(79.87 KiB) Downloaded 307 times

Place that in the automation folder and overwrite the existing lua51.dll . You should now have 2 dll's lua51.dll and lua5.1.dll

Run automation again, you should get this:

Init
Lua Version: "Lua 5.1"
Lua: No jit found

Now delete the scripts folder and run Automation, and see if the crash persists.

I hope that all makes sense?

[_Azza]

Shit man, It worked after following all of your steps.

This mean that I will have to repeat this process after every new patch update?

Cheers for your help, much appreciated.

[zeussy]

So it worked after applying that lua51.zip? And all of the console steps matched? Display the same text as I quoted?

Could I get a dxdiag from you? http://wiki.automationgame.com/index.ph ... ation_File

The cavaet with this, is you are now using normal lua, not luajit. Which can result in significant slower performance. The real question is why luajit is not working for you.

For future updates you only need to apply the last zip file, and replace our lua51.dll. You may not need to do this until Steam detects a change in the updates lua51.dll file compared to the previous update. I could be wrong, still learning quite how that updater works, but that is what it feels like.

[zeussy]

Also if I can get a dxdiag from disturbed as well that would be appreciated.

[_Azza]

Yeah, I followed your steps, written perfectly and I did get the correct messages pop up in the cmd window.

Here is my DxDiag.txt

[RedRiot]

I've got a different problem with the Steam version: the game starts and runs fine, but at every start it tries to re-install DirectX and .NET FX 3.5. I use Win XP, maybe that's the reason of the errors - maybe that's why it's not possible to install the latest DirectX version and my .NET FX install seems to be messed up a little bit. I downloaded and run the .NET FX repair tool from Microsoft - no success, still hasn't managed to apply the 3.5 update.

Anyway, after the failed DX and .NET FX installs Automation runs fine! My only pain is that I have to wait at every game starts those two long install attempts. Is there any way to remove the DirectX and .NET FX check/install procedure from the start-script of the game? Thank you in advance!

[zeussy]

I've got a different problem with the Steam version: the game starts and runs fine, but at every start it tries to re-install DirectX and .NET FX 3.5. I use Win XP, maybe that's the reason of the errors - maybe that's why it's not possible to install the latest DirectX version and my .NET FX install seems to be messed up a little bit. I downloaded and run the .NET FX repair tool from Microsoft - no success, still hasn't managed to apply the 3.5 update.

Anyway, after the failed DX and .NET FX installs Automation runs fine! My only pain is that I have to wait at every game starts those two long install attempts. Is there any way to remove the DirectX and .NET FX check/install procedure from the start-script of the game? Thank you in advance!

This is a Steam Bug, Go into the Steam\SteamApps Folder, find the file: appmanifest_293760.acf

Open it with notepad. and Delete the Text between the { } below "InstallScripts".

[zeussy]

_Azza,

The next update may have a proper fix for your issue.