EXE no response after open and close by itself shortly

Enscape Wishlist, Issues, Discussions Enscape :: Issues
1

I had a EXE exported in January this year.

it can run on one PC but cannot run on another PC..

The EXE will close shortly by itself after open.

however it can open recently exported EXE.

It is the PC spec that Dose not run Enscape EXE :

Product :Alienware Aurora R8

OS : win 10 pro 64 bit

CPU : i7-9700K

mem : 32G

graphic card : NVIDIA RTX 2080 8G

driver : 431.60 (updated today)

it is the PC spec that runs the old EXE:

Product : DELL laptop

OS : win 10 pro 64 bit

CPU : i7-6820HQ

mem : 32G

graphic card : NVIDIA M4000M

driver : 418.81

Very odd!

we export our projects in EXE as archives, so we tend not to re-export EXE tho it might solve the problem.

I believe there is a workaround

if this issue persist it will cause some trouble :frowning:

please help me to resolve it!

Thanks!

2

@Eric_Hsu - On an unrelated note: How do you like the Aurora R8 so far? We got one as a VR workstation (same spec as you) but returned it due to massive overheating issues, noise concerns and finally hardware failure. Did you run into any problems with yours yet?

3

@Eric_Hsu Sorry to hear that. The problem with exported standalone applications can be that issues with new driver, which we fixed in the proper application are still present in the standalone, since it is effectively a canned Enscape from the time it was created.

Nevertheless, can you send the last log files from the machine where it did not work. To do that open the file exporter and go to %APPDATA%\Enscape\Data\Logs copy the latest .log and .dmp files. (There may not be any .bmp, which is a good thing.) Zip the files and send them to support@enscape3d.com and reference this forum thread. We will have a look at them and see if we can do something.

4

Thanks, I will send a mail,
I also paste the log here for reference, since it is quite short

7-29 12:19:10.730 [normal] Starting Enscape 2.4.1.2-gf81592b
7-29 12:19:10.732 [normal] Executable path: "C:\Users\hsuyce.AS\AppData\Local\Temp\EnscapeStandalone_cln1vvlr.yz4\Bin64\EnscapeClient.exe"
7-29 12:19:10.732 [normal] Max number of threads available: 8
7-29 12:19:10.732 [normal] Microsoft® Windows® Operating System 10.0.17763.1
7-29 12:19:10.735 [warning] Could not load RPCapi.dll
5

Thank you we will look into it.

6

Hi, I encounter another one that failed to open, and managed to get a log with more info.

I paste here for ref, I also sent an email to support team.

8-12 15:03:14.318 [normal] Starting Enscape 2.4.1.2-gf81592b

8-12 15:03:14.327 [normal] Executable path: “C:\Users\hsuyce.AS\AppData\Local\Temp\EnscapeStandalone_lxcfsohz.wpd\Bin64\EnscapeClient.exe”

8-12 15:03:14.327 [normal] Max number of threads available: 8

8-12 15:03:14.327 [normal] Microsoft® Windows® Operating System 10.0.17763.1

8-12 15:03:14.330 [warning] Could not load RPCapi.dll

8-12 15:03:14.770 [normal] GLVendor: NVIDIA Corporation

8-12 15:03:14.771 [normal] GLVersion: 4.2.0 NVIDIA 431.60

8-12 15:03:14.771 [normal] GLRenderer: GeForce RTX 2080/PCIe/SSE2

8-12 15:03:14.771 [normal] Context flags: 0x1

8-12 15:03:14.790 [normal] AvailableTextureUnits: 32

8-12 15:03:14.928 [normal] Running in release mode.

8-12 15:03:15.245 [normal] TextureDataManager finished memory upload of updateTextureData: 0 MB in 0 ms.

8-12 15:03:15.304 [normal] Resize framebuffer to: 1264 681 estimated expected memory requirements: 58, memory requirements change by 58, available video memory: 4699

8-12 15:03:15.306 [normal] Resize framebuffer to: 1264 681 estimated expected memory requirements: 18, memory requirements change by 0, available video memory: 4673

8-12 15:03:15.520 [normal] Resize framebuffer to: 320 180 estimated expected memory requirements: 0, memory requirements change by 0, available video memory: 4525

8-12 15:03:15.531 [warning] could not load config C:\Users\XXXXXXXX\AppData\Local\Temp\EnscapeStandalone_lxcfsohz.wpd\userPost.cfg

8-12 15:03:15.641 [normal] Update statistics MaterialDataManager : Added 0 Removed 0

8-12 15:03:15.641 [normal] Largest instance counts:

8-12 15:03:15.641 [normal] Auralization ApplySwitchBuffer() complete!

8-12 15:03:15.641 [normal] Update statistics ModelDataManager : Added 0 Removed 0

8-12 15:03:15.641 [normal] LightDataManager max index: 0 shadowmapped lights: 0

8-12 15:03:15.641 [normal] LightDataManager max index: 0 shadowmapped lights: 0

8-12 15:03:15.642 [normal] LightDataManager max index: 0 shadowmapped lights: 0

8-12 15:03:15.642 [normal] LightManager updateData() complete.

8-12 15:03:15.642 [normal] WorldDataManager::postUpdateObservers() - available video memory: 4522 MB.

8-12 15:03:17.941 [normal] ----- Start switching buffer -----

8-12 15:03:17.944 [normal] Update statistics MaterialDataManager : Added 9357 Removed 1

8-12 15:03:17.949 [normal] ModelRenderManager finished memory upload of reallocateModelDataResources: 109 MB in 1 ms.

8-12 15:03:17.972 [normal] Largest instance counts: 1

8-12 15:03:18.019 [normal] ModelRenderManager finished memory upload of reallocateModelEntityResources: 1 MB in 40 ms.

8-12 15:03:18.027 [normal] Auralization ApplySwitchBuffer() complete!

8-12 15:03:18.263 [normal] Update statistics ModelEntityManager : Added 9354 Removed 0

8-12 15:03:18.263 [normal] Update statistics ModelDataManager : Added 9354 Removed 0

8-12 15:03:18.267 [normal] TextureDataManager finished memory upload of updateTextureData: 0 MB in 0 ms.

8-12 15:03:18.268 [normal] LightDataManager max index: 0 shadowmapped lights: 0

8-12 15:03:18.268 [normal] LightDataManager max index: 0 shadowmapped lights: 0

8-12 15:03:18.268 [normal] LightDataManager max index: 0 shadowmapped lights: 0

8-12 15:03:18.268 [normal] LightManager updateData() complete.

8-12 15:03:18.268 [normal] WorldDataManager::postUpdateObservers() - available video memory: 3220 MB.

8-12 15:03:19.392 [normal] ----- Finished switching buffer -----

7

@Eric_Hsu , this behavior should be resolved already. Could you kindly try out our latest release as described here (re-export any standalone files) to see if you experience any further issues? :slight_smile: Thanks a lot.