Welcome to Steelbeasts.com

Register now to gain access to all of our features. Once registered and logged in, you will be able to contribute to this site by submitting your own content or replying to existing content. You'll be able to customize your profile, receive reputation points as a reward for submitting content, while also communicating with other members via your own private inbox, plus much more! This message will be removed once you have signed in.

Sign in to follow this  
Followers 0
Pak1979

SteelBeast 4.10 wont start after windows 10 creators update

I have installed the new "creators update" on my windows 10 x64 System.
And after the update steel beasts 4.10 wont start anymore.
a reinstallation of steel beasts and the newest codeMeter software brings no success.
All other Games and Programs on my system works fine and without problems...

Share this post


Link to post
Share on other sites

Do you use a time limited license or a dongle? If it's the time limited license, I wonder if the Windows update invalidated it somehow.

Share this post


Link to post
Share on other sites

Any errors or anything else like that pop up, or does it just do nothing? You might check the debug log ( Documents\eSim Games\Steel Beasts\logs ) to see if anything gets reported there, assuming SB loads far enough to do so.

Share this post


Link to post
Share on other sites

It do nothing. The Mouse cursor for loading rotate any seconds, but then came no reaction ... no screen or message pops up ...

in the task manager i can see the exe is starting but after a few seconds he close.

 

that is the complete text of the logfile

 

[07:58:23,922] WARN : -------------------------------
[07:58:23,922] WARN : Steel Beasts Log File v4.010
[07:58:23,922] WARN : Fri Apr  7 07:58:23 201 / 7220
[07:58:23,922] WARN : -------------------------------
[07:58:23,922] WARN : +--+ MEMORY USAGE INFO (SteelBeasts START):
[07:58:23,922] WARN : |  | Process: 290 MB (0 % of 128.0 TB total, 128.0 TB free) 290 MB min/180 MB max
[07:58:23,922] WARN : |  | Physical: 2.9 GB (18 % of 15.9 GB total, 13.0 GB free) 2.8 GB min/2.9 GB max
[07:58:23,922] WARN : +--+ Pagefile: 3.5 GB (19 % of 18.3 GB total, 14.8 GB free) 3.4 GB min/3.5 GB max

Share this post


Link to post
Share on other sites

Microsoft never fails to entertain.

 

I received a report yesterday from one of the programmers who had tested it, and it seems to be a genuine Microsoft problem at work here. At this point I have no recommendation. Since MS forces these updates on Windows users, and since users of the Home version can't even choose to delay the upgrade - well, get used to this. We can program around MS's antics only after we learn about them, and at the same time the feedback from the Home users drives the update development at Microsoft. A future patch will solve the problem, eventually. Until then you're fucked, sorry.

Share this post


Link to post
Share on other sites

Okay, seems like it's not so bad.

 

If you start SB via the "Troubleshooting -> Steel Beasts Pro PE (debug)" shortcut, is there some more log output? If so, could you please post it here?

Share this post


Link to post
Share on other sites

I don't think creators update has been released into the general windows update stream yet, at least I have not seen it.  At this point, you have to force install it from what I have read.

 

It may be too late for you now, but for anyone else that happens to read this - never be the first to install the newest release.  The MS insiders program is giving them a false sense of confidence in the quality of their releases.  There may be a million insiders tinkering with a load in a virtual machine, but there is more to it than that.  

 

The last big windows update broke a bunch of stuff like webcams, etc.  This one will probably not be any different.  

Share this post


Link to post
Share on other sites
Awards

Debug Log....

[14:56:44,587] TRACE: -------------------------------
[14:56:44,587] TRACE: Steel Beasts Log File v4.010
[14:56:44,587] TRACE: Fri Apr  7 14:56:44 201 / 15188
[14:56:44,587] TRACE: -------------------------------
[14:56:44,587] TRACE: +--+ MEMORY USAGE INFO (SteelBeasts START):
[14:56:44,587] TRACE: |  | Process: 291 MB (0 % of 128.0 TB total, 128.0 TB free) 291 MB min/180 MB max
[14:56:44,587] TRACE: |  | Physical: 2.5 GB (16 % of 15.9 GB total, 13.4 GB free) 2.4 GB min/2.5 GB max
[14:56:44,587] TRACE: +--+ Pagefile: 2.5 GB (14 % of 18.3 GB total, 15.8 GB free) 2.4 GB min/2.5 GB max
[14:56:44,587] INFO : Network logging alarm threshold set to '120'.
[14:56:44,587] INFO : Network logging alarm message age set to '5'.
[14:56:44,629] TRACE: Entered BuildDeviceList
[14:56:44,655] INFO : Valid mode: 2560 x 1440, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 1920 x 1440, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 1920 x 1200, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 1920 x 1080, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 1680 x 1050, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 1600 x 1200, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 1600 x 1024, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 1600 x 900, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 1366 x 768, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 1360 x 768, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 1280 x 1024, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 1280 x 960, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 1280 x 800, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 1280 x 768, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 1280 x 720, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 1152 x 864, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 1024 x 768, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 800 x 600, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 720 x 576, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 720 x 480, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] INFO : Valid mode: 640 x 480, Fmt=22, Beh=0x40, dpthFmt=77, devNum=0
[14:56:44,655] TRACE: Found device... Leaving BuildDeviceList
[14:56:44,658] DEBUG: WM_ACTIVATEAPP: 0x1
[14:56:44,668] DEBUG: WM_SIZE: 0x0
[14:56:44,670] DEBUG: WM_ACTIVATEAPP: 0x0
[14:56:44,671] TRACE: Called FindWindowRects
[14:56:44,671] DEBUG: Display name '\\.\DISPLAY1' - 0x5.
[14:56:44,671] INFO : Eyefinity configuration query failed for display name '\\.\DISPLAY1'.

[14:56:44,671] DEBUG: FindMenuDisplayArea: 0/0/0/0
[14:56:44,671] TRACE: Entered Initialize3DEnvironment
[14:56:44,671] DEBUG: AdjustWindowForChange: For windowed
[14:56:44,672] DEBUG: *** PresentationIntervals (0x0/0x80000000) NOT SUPPORTED! (Initialize3DEnvironment) ***

Share this post


Link to post
Share on other sites

On a normal log the very next item would be "[08:07:44,697] TRACE: CreateDevice succeeded". The log stopping right before that makes me suspect the issue might be related to the video drivers and/or Direct3D. You could try to update your video drivers, perhaps the Windows upgrade did something odd with the previously working drivers you already had installed.

Share this post


Link to post
Share on other sites

Posted (edited)

I have updatet the new NVIDIA 381.65  drivers yesterday.

 

Ok i found it....The Riva TunerStatisticServer from MSI Afterburner that runs in Background to display frames temps core speed and other data.....It is the problem,.

After deactivate it in steelbeasts its starts and works fine.

Looks like the windows update have problems with the statistic server in combination with steelbeasts.

 

Before the update it worked allways, but the good is steelbeasts runs now after shut of the StatisticServer Tool that is great.

Edited by Pak1979

Share this post


Link to post
Share on other sites

Posted (edited)

Uh huh. Steel Beasts seems to not work well with anything that would intercept directX calls somehow. And this is somewhat annoying - can't use ReShade for example.

Edited by kraze

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0