DuchessGummybuns Posted April 25, 2015 Share Posted April 25, 2015 (edited) So, I ran into a problem that drove me so mad I did a clean install and over the course of a week retweaked my Skyrim build. That problem that caused me so much heartache was "Invisible fires." It was not missing textures or modded textures, it was not conflict with a refraction mod (as I thought,) it wasn't even a conflict of mods. After my work retweaking was done, I started my game up. I wiped the sweat from my brow and prayed. There had been no hiccups, no hurdles, no newly emerging issues, I was home free. After rebalancing my old saves for this new build, I was pleased. Running my happy butt around Nirn like a soft little newb, until I entered.... AN INN. And THERE, at MY feet! (How dare it!) A FIRE! THAT. WAS. INVISIBLE! I had no other option. I backed up My skyrim/pref.inis and the main .dll (I read that might cause it) and restarted the launcher, spawning new inis. Through trial and error I found Skyrimprefs.ini to be the culprit, but I had done nothing more to it than was required by STEP, my mods, and ENB. Nevertheless, I sifted until I found the rouge value. ENB says its effects REQUIRE bfloatpointrendertarget to be 1. REQUIRED. So, like the little blasphemous heathen I am, I reverted it to 0 to find my fires had miraculously reappeared and my ENB preset (Pinnapplevision) seems to working just fine. Why does bfloatpointrendertarget do that to my fires? What is its purpose in ENB? I am partly only posting this so that it will be easier for others experiencing my plight to find an explanation. Edited April 25, 2015 by DuchessGummybuns Link to comment Share on other sites More sharing options...
ZeroKing Posted April 25, 2015 Share Posted April 25, 2015 (edited) As the name's parameter indicate, it enables floating point numbering. Skyrim (and many other games) do not allow for that, so a lot of shaders (in-game or post-process) lose accuracy (at the gain of performance) when it's disabled. You need this parameter enabled for ENB to function properly. If the opposite happens, you should consider generating new Skyrim.ini and SkyrimPrefs.ini files (and yes, PINEAPPLEVISION ENB needs this parameter set to 1). Your .ini files probably has other settings that are corrupted and/or incompatible, and just happens to be apparently corrected with you changing one setting on and off. Skyrim's engine is stupid that way. EDIT: For further information. A render target is a method to force scenes to be render in a memory buffer, where you can manipulate effects (ie. shaders) instead of having it rendered in the back buffer or frame (framestore) buffer. This is especially true when you are manipulating an engine's exclusive features that might be turned off by default. Edited April 25, 2015 by ZeroKing Link to comment Share on other sites More sharing options...
DuchessGummybuns Posted April 25, 2015 Author Share Posted April 25, 2015 I have no way around it. Everything vanilla + bfloatpointrendertarget=1 = no fire. Link to comment Share on other sites More sharing options...
ZeroKing Posted April 25, 2015 Share Posted April 25, 2015 My only other suggestion is that you use the particle patch from Boris's website (the author of ENBSeries). If not, I'd also suggest ensuring that you are using the appropriate ENB binary .dll for that ENB. Link to comment Share on other sites More sharing options...
DuchessGummybuns Posted August 2, 2015 Author Share Posted August 2, 2015 Mmm, no dice. It didn't do anything. Link to comment Share on other sites More sharing options...
Recommended Posts