Karlstens
Member
Hi all,
At first I thought my game was failing to compile, but with no errors listing in the logs it became a bit of a mystery. And testing other apps in my codebase revealed that even my simple apps were failing to compile - or so I thought. Exiting and restarting GMS2 didn't fix the issue, neither did logging out my Windows session. But a computer restart seems to address the problem *most* of the time - I haven't fully figured out the issue which is why I'm posting here.
But thankfully just now, I have discovered that it's not that the game fails to compile, instead of the usual compile time of say 5 seconds - I have to wait without notice about 30-60 seconds before the game displays. The process where the wait occurs is on the last line; X://windows/x64/Runner.exe
After approx 30-60 seconds, then the game displays and the logging continues as per normal;
This issue started a month ago, possibly with the latest Windows 10 update? Interestingly both the release GMS2 and the Beta version start having this problem at the same time. It's a bit of a pain, so would be keen to hear if anyone else is experiencing this, or ways to resolve it. I've started configuring Windows Security to make exceptions to GMS2 exe and sub-directories, but problem persists...
At first I thought my game was failing to compile, but with no errors listing in the logs it became a bit of a mystery. And testing other apps in my codebase revealed that even my simple apps were failing to compile - or so I thought. Exiting and restarting GMS2 didn't fix the issue, neither did logging out my Windows session. But a computer restart seems to address the problem *most* of the time - I haven't fully figured out the issue which is why I'm posting here.
But thankfully just now, I have discovered that it's not that the game fails to compile, instead of the usual compile time of say 5 seconds - I have to wait without notice about 30-60 seconds before the game displays. The process where the wait occurs is on the last line; X://windows/x64/Runner.exe
Code:
Writing Chunk... STRG
Stats : GMA : Elapsed=770.4566
Stats : GMA : sp=2,au=0,bk=0,pt=0,sc=3,sh=0,fo=0,tl=0,ob=4,ro=1,da=0,ex=0,ma=5,fm=0x200A0090EA40020
DoSteam
Igor complete.
[Run] Run game
Options: Z:/Health_Arm_29372175_FD75C8D5\MainOptions.json
X://windows/x64/Runner.exe -game "Y:/Health_Armour_Shield_45F616EC_VM\Health_Armour_Shield.win"
Code:
Attempting to set gamepadcount to 12
DirectX11: Using hardware device
Collision Event time(microsecs)=6
Total memory used = 7942642(0x007931f2) bytes
**********************************.
Entering main loop.
**********************************.
Setting scheduler resolution to 1
This issue started a month ago, possibly with the latest Windows 10 update? Interestingly both the release GMS2 and the Beta version start having this problem at the same time. It's a bit of a pain, so would be keen to hear if anyone else is experiencing this, or ways to resolve it. I've started configuring Windows Security to make exceptions to GMS2 exe and sub-directories, but problem persists...