![]() This game doesn't have an OS check in order to punish people who use Windows versions older than 10. Originally posted by kilicool64:Okay, I think this is getting a bit out of hand. The real "♥♥♥♥♥" here is over the game ENGINE developer doing this. And while they could likelyh disable that feature, that's beyond the scope of what they were being paid to do. The error message is there as part of a b uilt-in OS version check in the game engine. They didn't add it and can't "remove" it without switching to a different game engine (which I suspect would be fairly easy, but would require quite a bit of "rote" effort.) The game devs used a third-party engine which has those "features." It'd be nice if an option to disable this check was added, but this is a serious overreaction. It's just an unfortunate side effect that this gets in the way of attempts to make the game work in spite of its dependency on DirectX 12. So they figured giving such people an error message about their OS being too old was preferable to whatever kind of error would occur if the game actually tried to use DirectX 12 when it's unsupported. The developers simply thought the game generally wouldn't work on such versions due to its DirectX 12 requirement. ![]() Okay, I think this is getting a bit out of hand. Originally posted by Vamp:Adding OS checks for simple games like this just makes me hate the developers and shun their software. it comes down to forensic work by end-users. All of about ten minutes of effort, frankly.Īnd even easier for the game engine developers, to simply disable that.īut neither will happen. ![]() or the game engine documentation, for that matter. into the program executable directory.Įasy as pie for a programmer with access to the Windows documentation. The trick to this is to figure out what DLL in Windows contains the "check" function which is being used, and to put a tweaked copy of that DLL. the game still checks for the "right operating system" and prevents execution if the "wrong operating system" is reported. at least theoretically.īut he's prevented from doing so by the hard-coded "OS version check" "feature." Even if he can theoretically translate every DX12 call into a VULCAN call. The OP here has a means of getting around the DirectX12 requirement. Yes, they used an off-the-shelf engine which "requires DirectX 12." But the engine they used also includes an "OS version check" "feature." ANY DX12 version prior is compatible with any Win10 or Win7 versions.īut this Pixel game really *need* that Raytracing. Originally posted by joridiculous:Its not the Win10 things being the problem, its the stupid decision to make it DX12, and specifically DX12.2 dependent.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |