error and crash omn startup: failed to initalize renderer

[MrBlueBeetle22]

so, im having an issue where I gte an error durign game startup, and I think know whats casuing it, but I cant figure out how ti fix it|

in Documents>My games> FalloutNV the Rendererinfo file is blank, ive tried using steam to verify the files, still blank, luahcign the game without NVSE, still blank

howevre, when I lunach the game in windowed mode, the file is no lomnger blank, but when i go back to fullscreen, it uit goes blank again 0kb file size, no text (no using oen tweak to have winodwed fullscreen is not an option for me)

I tired running the gae in windowed and settig the file to read only, but the game mad eit blank and refused to start in fullscreen anways

I am tota;ly at a loss, please help me fix this

[MrBlueBeetle22]

also sorry for bad typing

[dubiousintent]

That file gets created when you run the "FalloutNVLauncher" program, which should only be needed when you initially setup the game so it detects your hardware. (I would suggest you do this outside of any "mod manager" if you are having problems attempting to do so while in one.) Once you have done that, you should be starting the game by running the "FNV4GB Patcher" modified "FalloutNV" program. That will automatically detect and launch NVSE if you have it installed.

 

Which version of Windows?

 

Where do you have the game installed (full path please)?

 

What mod manager (if any) are you using? (I'm guessing that is why sometimes you see that file and other times you don't, though it is very strange behavior.)

 

If the problem persists, then see either the 'Solutions to Starting the game problems' or the 'Solutions to "Crash To Desktop" (CTD) problems' sections in the wiki "Fallout NV Mod Conflict Troubleshooting" guide.

I recommend anyone read the entire "FNV General Mod Use Advice" article to understand the differences between this game and others you may have experience with; especially if this is your first attempt to play a modded FNV or it's been more than a year since you last did so.

Why do you think you cannot use "One Tweak" to run your game in fake fullscreen mode? (There are other options to do the same thing, such as "Borderless Gaming".)

 

Take your time to clean up your typing. You are not likely to get an immediate response, and if we can't make out what you intend to say, we are delayed asking for clarification.

 

-Dubious-

[MrBlueBeetle22]

ok some more info

I am rubbign windows 10 oon a Imac 2018 with maxed internals using bootcamp

new vegas is intsalled in my main drive in th defeault plcae steam puts games, and I ma using vortex

[dubiousintent]

Macs running "bootcamp" are outside of my experience. My understanding that it is basically a "Windows partition" on your Mac's disk drive that you then boot into instead of the Apple OS, in the same manner one can "dual boot" a PC between Windows and Linux.

 

That being the case, you should be able to treat it exactly the same as a fully "Windows 10" PC as far as the software is concerned. Which means, everything in "Installing Games on Windows Vista+" and "General Mod Use Advice" applies. First and foremost of these is: do not install to the default location. The "Installing Game" article covers how to move it, or just uninstall game and reinstall from scratch to the new location.

 

The following entries in the wiki 'Fallout NV Mod Conflict Troubleshooting' guide specifically address known Win10 problems:
* 'Issue: NVSE - fails to load after update KB4058043 to Win10 FCU (v1709)'
* 'Issue: Incomplete save game load' (NVSR related)
* 'Issue: Vanilla game Hangs on startup'; specifically "Cause-1" regarding DirectX9 drivers.
* 'Issue: "Full screen mode" exhibits CTDs and stutters or micro-stutters'
* 'Issue: Recent (post-Win10 FCU) CTDs after 10-20 minutes of play' (NVSR related)
* 'Issue: Lag or "micro stutters" even with "New Vegas Stutter Remover" installed (or not)'. In particular "Cause-4" regarding video card settings. The latest video drivers may not be the best suited to an older game like FNV. All vendors drop testing of old games at some point. Backwards compatibility is never guaranteed, much less "optimization".
Also, "Cause-7" regarding "Superfetch" and "File search indexing". Windows updates will often reset these back on.
* 'Issue: Win10 Screen tearing in "Borderless Windowed Mode"'
* 'Issue: ENB Support for Windows versions later than Win7'
* 'Issue: Problems using ENB/SweetFx on Windows 10'

If you are still having issues with the RenderInfo file after moving the game out of the default install location and after running the Launcher outside of Vortex, take that issue up with their support forum.

 

-Dubious-

[MrBlueBeetle22]

oki I figured it out, I was the new ENB I intsalled, got rid of it and the issue stopped