New Viewer will not run for me on Windows 10

starflower

New member
I wonder if this is an issue that only I am having? Neither 1.8.10 nor 1.8.9 will run for me on Windows 10. It does not seem to be blocked by Avast or anything in Windows as far as I have been able to discover. I installed it in C:\Program FIles\Dayturn and this was weird because I had to manually create that folder since no location was suggested as is usually the case. The little box appears saying it is about to run and then it just doesn't. Any ideas? Many thanks!
 

Geir Nøklebye

World Builder
Staff member
Is your system language other than English? Some users have reported it will crash immediately if the system language is set to Dutch.

There might also be issues with correct detection of graphics drivers. There is an improvement for that in the next version which should only be a few days away.
 

starflower

New member
No, I have it set to English. Maybe it's to do with my graphics driver or card then. Thank you very much for the speedy reply. I look forward to seeing the viewer working :)
 

Geir Nøklebye

World Builder
Staff member
Has it ever run before or is this your first attempt?

...usually when it can't even start it is the graphics driver barfing on the 32-bit viewer, or fmod audio drivers being unhappy with your hardware for some reason.
 

starflower

New member
First time, yes. I've run all the other viewers known to science on all major platforms at some point or other! :-D I suppose I could root around in some logs somewhere to see if I can find the reason...?
 

Geir Nøklebye

World Builder
Staff member
You could try but if it crashes this early it hardly has time to even write a log entry. The Windows error log might be the only place to look.

If you have a virus/malware scanner you might want to check that log too in case it kills it.
 
Last edited:

Geir Nøklebye

World Builder
Staff member
I forgot to ask if it was the RLV or non RLV version you tried.

... I tested the viewer in an early beta of Win11, and it crashed immediately. So there might be a clue there to look at for me also.
 

Geir Nøklebye

World Builder
Staff member
OK.

I have a new Windows non-RLV build with changes to the vsync setting that according to recent LL code changes is better for Windows. (the improved setting will crash the macOS version immediately)

You can download it from
Link removed because it is now released. Release in Resources as versions 1.9.0 and 2.8.1 for Windows and macOS respectively.
 
Last edited:

starflower

New member
Event Viewer > Windows Logs > Application

Faulting application name: DayturnViewer.exe, version: 1.9.0.63573, time stamp: 0x614af087
Faulting module name: DayturnViewer.exe, version: 1.9.0.63573, time stamp: 0x614af087
Exception code: 0xc0000005
Fault offset: 0x0108831e
Faulting process ID: 0x2628
Faulting application start time: 0x01d7b075f0a949f2
Faulting application path: C:\Program Files\Dayturn\DayturnViewer.exe
Faulting module path: C:\Program Files\Dayturn\DayturnViewer.exe
Report ID: 1f7c5f6e-cebb-4379-95a8-20636f6a4f37
Faulting package full name:
Faulting package-relative application ID:

This is all I can find. It's still doing it in 1.9.0, unfortunately. It seems to be trying to access some memory that it shouldn't, as far as I can gather from googling. Not sure which memory or how. Does that help at all?
 

starflower

New member
I also notice there is no app data in C:\Users\Starflower\AppData\Local\Dayturn, which seems strange since there is for Firestorm and other viewers. Is it somewhere else? Perhaps that's not relevant?
 

Geir Nøklebye

World Builder
Staff member
I also notice there is no app data in C:\Users\Starflower\AppData\Local\Dayturn, which seems strange since there is for Firestorm and other viewers. Is it somewhere else? Perhaps that's not relevant?
It only means it never got to the stage of populating that directory.
 

Geir Nøklebye

World Builder
Staff member
It is also possible there is a file system inconsistency on your disk because the very first thing it does is creating the virtual file system and then writing logs, config and settings files. If it for some reason cannot write to disk it would crash at that stage
 

starflower

New member
It refuses to turn off DEP for DayturnViewer.exe and all others in that directory. I am trying out all the other methods suggested by the link that you sent: SFC and so on. Thanks, I'll keep trying :)
 

Members online

No members online now.
Top