|
|
Post by diamondback on Oct 12, 2019 23:17:53 GMT
Good evening all, I installed CDE on a new laptop, an Acer Nitro 5, but didn't get very far. The game crashed to desktop with a C++ runtime error anytime the railguns I'd made struck anything. I tested 1m long to 4m long, 1gram to 25gram osmium radiation shield payloads traveling at 20-50 km/s. My previous laptop had no problem handling these impacts regularly. After checking the FAQs, I tried to enable windowed mode, causing this:  This is the main screen after disabling fullscreen. Restarting the game brings me right back here. Manually changing the preferences to fullscreen=true restores it to full screen. Anyone have these kinds of issues before? Attachments:
|
|
|
|
Post by cipherpunks on Oct 13, 2019 4:48:42 GMT
I installed CDE on a new laptop, an Acer Nitro 5, Looks like bad GPU drivers issue to me. There were 2 variants of that Nitro 5 thing: one with Intel 9th gen. CPU + nVidia's GTX 1660 Ti (which I would not advise to buy), and the other with AMD insides (drivers for that can be tricky too). Which one you have? |
|
|
|
Post by diamondback on Oct 13, 2019 16:37:44 GMT
Mine has an AMD video card. I’ve never had a problem with any other games.
|
|
|
|
Post by diamondback on Oct 13, 2019 17:16:14 GMT
Sure enough the windowed issue was fixed by installing the latest AMD management software, mine was telling me my drivers were good to go but I didn't have the latest settings program.
However, my game still CTD either when I fire the above railguns or on first impact. I thought those were within the games abilities, I guess not.
|
|
|
|
Post by cipherpunks on Oct 14, 2019 2:19:40 GMT
Even after properly replacing GPU driver stack (using Display Driver Uninstaller a.k.a DDU), you actually have 2 (two) full cans of worms still. One is AMD's platform per se - it has not one firmware but several. For example, make sure that the AGESA is up to date, etc. Another is Windows 10. I won't comment on that one much because it'll look wrong if moderator swears. One thing you may try is researching if all the drivers needed are available for said hardware for older Windows cores (Windows-7 alike; that usually includes server versions) and if so - install older Windows core and try with that. I doubt above mentioned availability of drivers, though. Also you can try to turn off any and all in-CPU-bug-mitigation patches/workarounds. That includes going to EFI and switching off relevant parts there. I doubt running CoaDE in VM is feasible, so the last thing you can try is to install proper UNIX, install Wine in it, and (after installing DirectX) run wine CDE.exeWhat I've written above presumes that you - like any sane person - do not have resident "antivirus" slowdown mechanism installed. If that is not the case - then you should know that probability of all the code you run there modified/tampered-with in-flight rises dramatically. That said, there should be no reason to make railguns with such "standard" payloads. No need to multiply unnecessary entities. If you need sub-gram projectiles - just edit the limits. If "needle-guns" work as "cheating" - just wait for patch that fixes that, or apply self-restraint. Or do You believe that regular payload-less railgun model does not work as intended?... |
|
