Jump to content

Problem with ENBoost


scissorhands

Recommended Posts

As you may have guessed from the title, I recently installed ENBoost. It seems to be working, except for one fatal flaw; I get the following message:

 

Error! bFloatPointRenderTarget=1 is not set in SkyrimPrefs.ini or you have multiple copies of the file.

 

It is set. I searched through the files to make sure there wasn't anything else that contained the phrase 'bFloatPointRenderTarget' - there isn't anything apart from the readme. I'm really stumped as to what the problem is. Could someone help?

 

If it helps, I should add that I tried installing ENBoost a little while ago, but I installed it wrong. Still, I thought I deleted all the old ENB files and replaced them, so that shouldn't be a problem.

Edited by scissorhands
Link to comment
Share on other sites

If you use Mod Organizer(MO), it keeps its own copy of SkyrimPrefs.ini and that file should be modified via the MO ini editor.

If not, make sure the ini file you are modifying is [YourUserName]\My Documents\My Games\Skyrim\SkyrimPrefs.ini.

 

If the above two are okay, open your ini file in Notepad (or whatever) and Search for that entry; there may be more than one and the entry later in the file will take precedence.

 

If all else fails, check for ini files in your Skyrim\Data directory. There may be a [someModName].ini file which sets the entry and overrides the default setting.

Link to comment
Share on other sites

Okay, lets clarify something then. It has become popular to refer to an enbseries+ENB preset install as "ENBoost". Technically, that is incorrect; there is a specific enbseries mod called ENBoost which was specifically made by Boris back in 2013 to implement the memory support routines he coded into his enbseries, without any graphics processing support. The mod consists of a single enblocal.ini file tailored for specific video cards which overrides a normal enbseries install enblocal.ini file. For an actual ENBoost mod install, the enblocal.ini has UsePatchSpeedhackWithoutGraphics=true, which disables graphics processing. In this case (actual ENBoost mod installed), you will NOT receive the error: "bFloatPointRenderTarget=1 is not set in SkyrimPrefs.ini or you have multiple copies of the file"

 

If you are just running an enbseries install in ENBoost mode (No ENB preset installed and UsePatchSpeedhackWithoutGraphics=true in your enblocal.ini file), you will NOT receive the "bFloatPointRenderTarget=1 is not set..." error.

 

If you are referring to an enbseries plus an ENB preset install as "ENBoost", then your problem is valid.

 

Note that the enblocal.ini file is common to all three of the above scenarios (Actual enbseries+ENBoost install, an enbseries only with enblocal.ini set to ENBoost mode, or a full enbseries+ENB preset install) and often gets overwritten when installing new enbseries or ENB presets.

 

After saying all that, I originally assumed that you have an enbseries + ENB preset (Like RealVision) and it is not working because of the bFloatPointRenderTarget=1 issue.

 

So, I need to ask; Are you trying to get a full enbseries+ENB preset for graphics working, or do you want an actual ENBoost/ENBoost mode (without graphics processing)?

 

EDIT: If you just want ENBoost (no graphics processing), go to your Steam\SteamApps\common\Skyrim directory. Find the enblocal.ini file and open it in Notepad (or whatever). The following are default (AMD) entries from ENBoost 5.0. The main entries to check are under [GLOBAL], [PERFORMANCE], [MULTIHEAD], [MEMORY], and [FIX].

 

 

 

[PROXY]
EnableProxyLibrary=false
InitProxyFunctions=true
ProxyLibrary=other_d3d9.dll

[GLOBAL]
UsePatchSpeedhackWithoutGraphics=true
UseDefferedRendering=false
ForceFakeVideocard=false

[PERFORMANCE]
SpeedHack=true

[MULTIHEAD]
ForceVideoAdapterIndex=false
VideoAdapterIndex=0

[MEMORY]
ExpandSystemMemoryX64=true
ReduceSystemMemoryUsage=true
DisableDriverMemoryManager=false
DisablePreloadToVRAM=false
EnableUnsafeMemoryHacks=false
ReservedMemorySizeMb=256
VideoMemorySizeMb=xxxx <---- Set to the vram amount in MB on your video card (2G = 2048)

[WINDOW]
ForceBorderless=false
ForceBorderlessFullscreen=false

[ENGINE]
ForceAnisotropicFiltering=true
MaxAnisotropy=16
EnableVSync=false
AddDisplaySuperSamplingResolutions=false

[LIMITER]
WaitBusyRenderer=false
EnableFPSLimit=false
FPSLimit=60.0

[iNPUT]
//shift
KeyCombination=16
//f12
KeyUseEffect=123
//home
KeyFPSLimit=36
//num / 106
KeyShowFPS=106
//print screen
KeyScreenshot=44
//enter
KeyEditor=13
//f4
KeyFreeVRAM=115

[ADAPTIVEQUALITY]
Enable=false
Quality=1
DesiredFPS=20.0

[ANTIALIASING]
EnableEdgeAA=false
EnableTemporalAA=false
EnableSubPixelAA=false
EnableTransparencyAA=false

[FIX]
FixGameBugs=true
FixParallaxBugs=true
FixAliasedTextures=true
IgnoreLoadingScreen=false
IgnoreInventory=true
FixSsaoWaterTransparency=true
FixSsaoHairTransparency=true
FixTintGamma=true
RemoveBlur=true
FixSubSurfaceScattering=true

 

Edited by Lord Garon
Link to comment
Share on other sites

I've done all of that. I'm absolutely certain that the SkyrimPrefs.ini file (which there's only 1 copy of) is the only one that contains 'bFloatPointRenderTarget'. Yet I still get the message...

There are 2 copies of Skyrimprefs.ini for Skyrim...

 

One is located here>>>.......Steam\steamapps\common\Skyrim\Skyrim <<<DO NOT edit this file.

 

The correct file is here>>>>.......\Documents\My Games\Skyrim

BUT for MO users the correct file is in their Profiles folder for MO.

Link to comment
Share on other sites

 

There are 2 copies of Skyrimprefs.ini for Skyrim...

that. I'm absolutely certain that the SkyrimPrefs.ini file (which there's only 1 copy of) is the only one that contains 'bFloatPointRenderTarget'. Yet I still get the message...

 

One is located here>>>.......Steam\steamapps\common\Skyrim\Skyrim <<<DO NOT edit this file.

 

The correct file is here>>>>.......\Documents\My Games\Skyrim

BUT for MO users the correct file is in their Profiles folder for MO.

 

THANK YOU! I didn't know about the other file (I assumed all the relevant files would be in the same place). I changed the setting in that file and set it back to 0 in the wrong file. Now it works perfectly :)

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...