protoftw Posted January 6, 2023 Share Posted January 6, 2023 (edited) Okay so...After updating the drivers, I'm getting this freaking error & I can't fix it. UD3DRenderDevice::SetRes <- UWindowsViewport::TryRenderDevice <- UWindowsViewport::OpenWindow <- UGameEngine::Init<- InitEngine Before replying: -Directx is updated. -Options.ini deleted & tested -Temporary files deleted. -Drivers reverted back before update but still the same error occurs. -Clean c6 client + system tested. -DPI Settings changed and tested -Compatibility on l2.exe changed and tested. -Even without drivers the same error occurs. Any suggestions? I'm really done trying, I've searched like 50+ forums but those solutions dont seem to work for me. I'm waiting for your replies, thank you *I've restored my drivers and went back and forth numerous times but it didnt seem to work. As for one last try , i've decided to try again. I've restored to a very old driver, and then decided to update my drivers again through amd. Factory Reset Settings (Selected) Keep User Settings (Deselected). Also I've cleared some cache to numerous programs i use that might have to do with the resolution of the screen and it seemed to work. Edited January 7, 2023 by protoftw misspelling Link to comment Share on other sites More sharing options...
Bumble Posted January 6, 2023 Share Posted January 6, 2023 (edited) This isn't the right section for this, but I imagine it's something with NWindow.dll or Engine.dll. Maybe try different versions? It could also be the resolution settings in your L2.ini that are wonky Edited January 6, 2023 by Bumble Link to comment Share on other sites More sharing options...
protoftw Posted January 6, 2023 Author Share Posted January 6, 2023 2 minutes ago, Bumble said: This isn't the right section for this, but I imagine it's something with NWindow.dll or Engine.dll. Maybe try different versions? I've tried so many different files but nope...nothing happens. Link to comment Share on other sites More sharing options...
Bumble Posted January 6, 2023 Share Posted January 6, 2023 (edited) Which resolution are you using on your computer? Did you see if anything weird is going on in L2.ini? Is your graphics driver forcing certain settings for Lineage 2 now? Edited January 6, 2023 by Bumble Link to comment Share on other sites More sharing options...
protoftw Posted January 6, 2023 Author Share Posted January 6, 2023 I've changed to different resolutions on my pc to test if it runs but it wasnt. Currently using 1920x1080. L2.ini seems fine. No lineage2 is deleted from graphics card menu. I don't know man. It's so fucking weird. Link to comment Share on other sites More sharing options...
Deazer Posted January 6, 2023 Share Posted January 6, 2023 19 minutes ago, protoftw said: I've changed to different resolutions on my pc to test if it runs but it wasnt. Currently using 1920x1080. L2.ini seems fine. No lineage2 is deleted from graphics card menu. I don't know man. It's so fucking weird. Try please my full unpack patch from Themida https://lucera2.com/data/LuceraTestPatch.zip Link to comment Share on other sites More sharing options...
protoftw Posted January 6, 2023 Author Share Posted January 6, 2023 2 minutes ago, Deazer said: Try please my full unpack patch from Themida https://lucera2.com/data/LuceraTestPatch.zip Thanks but it doesnt work . same error again -_- Link to comment Share on other sites More sharing options...
Nightw0lf Posted January 7, 2023 Share Posted January 7, 2023 whats your build and what programs running? l2 window fails to open resolution fail to set read only files? antivirus? alot of questions Link to comment Share on other sites More sharing options...
protoftw Posted January 7, 2023 Author Share Posted January 7, 2023 (edited) fixed. Edited January 7, 2023 by protoftw Link to comment Share on other sites More sharing options...
Destorion Posted January 8, 2023 Share Posted January 8, 2023 useless replies has been deleted, Please @Nightw0lf Next time try to calm down your attitude... Thanks... Link to comment Share on other sites More sharing options...
Nightw0lf Posted January 8, 2023 Share Posted January 8, 2023 (edited) nothing was wrong with my attitude the difference was in translation i could say "dont be an ass" or "dont be an asshole" its the same but the first is less offending and i sould have cut the word, so i apoligized but that was not a reason to remove his solution post its just correct way of saying in last post the solution to not be confuzing and then lock Edited January 8, 2023 by Nightw0lf Link to comment Share on other sites More sharing options...
Nightw0lf Posted January 8, 2023 Share Posted January 8, 2023 i am wondering what happens if he try to update his drivers again what happens then? Link to comment Share on other sites More sharing options...
Nightw0lf Posted January 8, 2023 Share Posted January 8, 2023 i mean after all this problems caused by a driver update and lineage stop working, the most possible reason is that he forgot some important driver to install, that if is installed now and he update the graphic card drivers might work? people should first identify their motherboards https://www.cpuid.com/ in case they dont know their models then google the motherboards company and download full drivers, just be carefull when updating bios. other than that if all drivers installed properly directx is very important https://www.microsoft.com/en-us/download/details.aspx?id=35 and windows updated fully there should be no problem at all, so its very weird Link to comment Share on other sites More sharing options...
Zake Posted January 8, 2023 Share Posted January 8, 2023 On 1/7/2023 at 3:16 AM, protoftw said: fixed. Well, anyway Link to comment Share on other sites More sharing options...
Recommended Posts