Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Example 03_materials crashes #11

Open
hoelzl opened this issue Jan 9, 2019 · 6 comments
Open

Example 03_materials crashes #11

hoelzl opened this issue Jan 9, 2019 · 6 comments

Comments

@hoelzl
Copy link

hoelzl commented Jan 9, 2019

Example 03_materials throws an unhandled exception from nvoglv64.dll when I try to run it. (Built from the latest master (00fc8af) using VS2017 on Windows 10 Pro 64 bit with GeForce GTX 1080 graphics card, driver version 417.35, 4k monitor.)

Unfortunately the exception details are not particularly helpful (at least to me):

Unhandled exception at 0x00000000678D0AD9 (nvoglv64.dll) in 03_materials_d.exe: Fatal program exit requested. occurred

Neither is the backtrace of the thread that raises the exception:

image

I tried to find debugging symbols, but it seems that nVidia does not provide .pdb files for their drivers.

Backtrace of the main thread:

image

The last two lines of the console log before entering the debugger are:

INFO: loading program filter/prefilter_envmap_v0 with options
INFO: loaded program c:/Users/tc/Programming/Games/Toy/mud/data//shaders/compiled/filter/prefilter_envmap_v0 id 19

I've also attached the full console log in case there is anything helpful in there: 03_materials_console_output.txt

The debug output is as follows:
03_materials_debug_output.txt

@hugoam
Copy link
Owner

hugoam commented Jan 10, 2019

Hi ! This one looks like it might be a GL driver issue. There is a leftover debug line which forces OpenGL mode whereas on windows you would probably want D3D: you can comment this line to try in D3D mode: https://github.com/hugoam/mud/blob/master/src/bgfx/BgfxSystem.cpp#L68

@hoelzl
Copy link
Author

hoelzl commented Jan 10, 2019

Thanks for the quick reply. Switching to D3D does indeed solve the issue.

@hugoam
Copy link
Owner

hugoam commented Jan 11, 2019

Does the crash still happen with last commit, and is it deterministic e.g crashes every time ?

@hoelzl
Copy link
Author

hoelzl commented Jan 11, 2019

The crash used to be deterministic, but with the latest commit (6ed1f1c) both OpenGL and D3d seem to work perfectly fine.

Actually, with this commit, example 14_live_gfx_visual is the only one that crashes on startup and 17_wfc crashes when I edit some values in the inspector pane. For some of the other examples the visuals seem to be not quite as intended, but the examples no longer crash or simply show black windows as they did in earlier commits, so your recent fixes have improved things considerably on my machine.

@hugoam
Copy link
Owner

hugoam commented Jan 11, 2019

Great, so this was probably also due to the outdated shaders. That leaves mostly the character skinning issue or is that one fixed also ?
Yeah, I'm still working on fixing the remaining examples that are broken and the few remaining bugs, it's been a while since I went on a bug fixing spree.

@hoelzl
Copy link
Author

hoelzl commented Jan 11, 2019

Unfortunately character skinning does not yet work with OpenGL although it's no longer quite as random. I'll add more information to #12.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants