Instant freeze on startup

[ElBretzelito]

Hi I tried every version, but they all do the same thing. I get the "Do you have unpacked game files?" window, but it doesn't matter what I answer. After that I can only see the black background of the mv appearing, the white areas around it where features should appear, but nothing loads, the program just freezes. If I wait long enough, I'll finally have the "NMSMV Has stopped working". Same computer as I play nms on, so I assume it's more than strong enough for a mv. I'm on windows 10

The only videos I could find about your model viewer were DaveUK's , and it seems like most people in the comments were running it with no issue. But I've seen two comments talking having similar probems to mine, and nobody seems to have found a solution.

[jackcarey]

I'm running into a similar issue with 0.90.7 & 0.90.7-hotfix on Windows 11. A blank white window loads, CPU & RAM get very high, then nothing happens no matter how long I leave it.

0.90.6 is a little better, asking me if I have any unpacked game files before it also freezes

[gregkwaste]

Sorry for the late reply @ElBretzelito, @jackcarey you can attach your log.out files just to see if the app indeed hung at some point.

At startup, after the app identifies the NMS installation directory, it tries to cache the contents of all the .pak files of the game. That may cause the app to hang but in reality it works on the pak files in the background.

Also I highly recommend you get the new version 0.91.1 which has received a lot of upgrades (moved to NET 6.0) with regards to rendering performance and some bug fixes related to other crashes.

Note that the new version is trying to work on the PAK files asynchronously so it should not cause any hangs (theoretically). In my case, with the game installed on an SSD this doesn't take more than 3-4 seconds for the process to finish.

[TalonGrayson]

Hey @gregkwaste - I'm late to the party, but I'm experiencing the same thing on Windows 11, NMSMV v0.91.1.

I've never done this before, so I'm not sure whether this is a user error. So, here's some info:

Prior to installing:

• Steam is installed on C: (SSD)
• NMS is installed on X: (partition of same SSD)
• I used NMS Modding Station to unpack X:\SteamLibrary\steamapps\common\No Man's Sky\GAMEDATA\PCBANKS files to a folder on V: (different SSD): V:\NMS Modding\Unpacked Files
• I have downloaded the latest MBINCompiler
• I have installed the Desktop Apps version of .NET 6.0
• Rebooted (old habits die hard)

Installation

• I downloaded v0.91.1 (latest release at the time of writing), and extracted it into a folder (V:\NMS Modding\NMSMV)
• I copied libMBIN.dll from MBINCompiler into the NMSMV folder (overwriting the old one)

First run

• Double click NMSMV.exe
• Respond "Yes" to the "Do you have unpacked game files"
• Select folder V:\NMS Modding\Unpacked Files

Result

• No NMSMV icon appears in my taskbar
• NMSMV appears in my Task Manager as WPFModelViewer (0% CPU, ~230 MB Memory, 0 MB/s Disk, 0 Mbps Network)
• I have left it in that state for 20-30 minutes, with no apparent change
• log.out (renamed as out.log, because github doesn't let me attach .out files)

Any help would be greatly appreciated 😄

[gregkwaste]

Hi there, thank you for the detailed report. Apparently the log.out was enough to figure out the issue XD

Rhetorical question @TalonGrayson, are you using an AMD graphics card?

[TalonGrayson]

Apparently the log.out was enough to figure out the issue XD

Ha, oh well, better to have too much info than too little I guess!

Rhetorical question @TalonGrayson, are you using an AMD graphics card?

Yeah, I am...

[gregkwaste]

Apparently the log.out was enough to figure out the issue XD

Ha, oh well, better to have too much info than too little I guess!

Rhetorical question @TalonGrayson, are you using an AMD graphics card?

Yeah, I am...

Open Bound_FS.glsl and delete line 10 : uniform vec3 color;

Restart the app.

Apparently the AMD driver does not like unused uniforms -.-

I'll push this fix on the next release

[TalonGrayson]

That fixed it for me. Thank you very, very much!

[gregkwaste]

I'm closing this issue. If you guys @ElBretzelito , @jackcarey still got any issues please open a new ticket.