False Alarm 0.9e-2 - Startup crash related to Windows 10?
#1
This issue has come to my attention: http://steamcommunity.com/app/276870/dis...656602575/

Quote:Crash Report: Dwelvers Alpha v0.9e-2
Running time: Hours: 0 Minutes: 0 Seconds: 11

____THREAD 1____
D3D::UtilReleaseRenderTargetTexture
D3D::CheckThreadLocker

CPU is I7 5820
GPU Geforce 970
16g memory
and i am using/testing windows 10

Before I upgrade my laptop to windows 10 to confirm and fix this issue I need to know if there are others out there with windows 10 that are experiencing the same issue with crashes.

If this is the case or not, please let me know, and if you could write down the systems specs as well it could really help Smile
Reply
#2
I'm not upgrading my main computer to Windows 10, but I have been thinking about upgrading the laptop since it has Windows 8.1 which I'm not all that happy with. I heard there were still a lot of bugs in Windows 10 on release, so hopefully they have made some improvements over the past month. At least they have a rollback option worst case.

[edit]

Upgraded from Windows 8.1 Pro to Windows 10 Pro. Dwelvers works exactly the same. Played it on game speed 9 to quickly get production rolling and test out the other features for the 20 minutes I had to spare. No additional issues to be seen past the current list of Bugs/Issues & Crashes. Yeah, I had to do that. Tongue
Reply
#3
I'm on 10 Pro, no issues starting up.

AMD FX4130
AMD Radeon HD 7870
8 GB memory
Reply
#4
Hmm, it seems someone solved this by downloading certain file that was needed? http://steamcommunity.com/app/276870/dis...6659300254
Spec: Win 10, ATI 7800 HD, res: 1280x1024x75. I support The Venus Project & Resource-Based Economy
Reply
#5
Hmm, I think the solution there is not related to the main problem in the topic.
Reply
#6
Rasmus I haven't found anyone on Steam forum complaining about that after I think 0.9e-3 release, maybe it's already been solved?
Spec: Win 10, ATI 7800 HD, res: 1280x1024x75. I support The Venus Project & Resource-Based Economy
Reply
#7
I think we can just add it as false alarm because I don't believe this is a windows 10 issue at all anyway.
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)