Jump to content

DoubleYou

Administrator
 View Profile  See their activity

  • Posts

    7,933

  • Joined

  • Last visited

 Content Type 

Everything posted by DoubleYou

  1. DoubleYou
    Mod Source: Papyrus Compiler Patch for x64 Systems by DoubleYou Description This patch allows you to compile Papyrus scripts when using the Creation Kit in conjunction with Mod Organizer when you're using a 64-bit computer. This patcher made in CodeFusion offset patches one single byte at 0x00000218 from 01 (AnyCPU mode) to 03 (32-bit only mode). More explanation can be found here: https://forum.step-project.com/topic/6214-howto-use-creationkit-from-mo/ Installation Extract Patcher to the Papyrus Compiler directory inside the Skyrim folder. Run Papyrus Compiler Patch for x64 Systems. Click Patch. Read log to verify file was successfully patched.A backup shall be created with a .BAK file extension. If you run into a permissions issue (possible even if run as admin), try copying both the patch and PapyrusCompiler.exe to your desktop and execute there, moving the new files back to this directory once complete. Uninstallation Delete PapyrusCompiler.exe from the Papyrus Compiler directory inside the Skyrim folder. Rename PapyrusCompiler.exe.BAK to PapyrusCompiler.exe inside the same folder Credits Thanks to Tannin42 for discovering this fix.
  2. DoubleYou
    Mod Source: Oblivion Project INI (opINI) by DoubleYou opINI Oblivion Project INI (opINI) is an attempt to restore decency to the Oblivion INI configuration file. Sadly, Bethesda screwed up its INI. You would think that their INI creation method via the Oblivion Launcher would be completely error free, as how could they mess up what essentially is a simple text file? but it isn't. It is chock full of uh-ah-choo! sneeze-worthy lines. Enter opINI. We spinned the file that Oblivion uses to create your presets, twirled it into a sensible order, and whirled away most of the errors. This removes a large portion of the obsolete and redundant lines that the Oblivion Launcher erroneously applies to the INI file. Installation: 1. Download the main file. 2. Run the installer. 3. Follow the on-screen instructions. 4. Read any warnings carefully! 5. Once the installer has completed, the Oblivion Launcher will automatically run to generate your new INI file. 6. Adjust your screen resolution and other settings as desired like normal. 7. If using Mod Organizer, copy the generated Oblivion.ini file to your \profiles\ directory. Once this is done, please add any and all desired tweaks, as these are NOT tweaked outside of default tweaks. This mod cleans up the INI creation process. It doesn't add tweaks. Archive Invalidation will need to be redone. Uninstallation: 1. Replace your Oblivion.ini file with the backup you should have made according to the warning in installation and go to step 3. If you neglected to heed my warnings, delete you Oblivion.ini file and go to step 2. 2. Run the Oblivion Launcher and adjust your screen resolution and other settings as desired like normal. 3. If using Mod Organizer, copy the generated Oblivion.ini file to your \profiles\ directory. 4. Eat salt and vinegar chips.
  3. DoubleYou
    Ah, well that explains the crashing with my INIs. You have uGridToLoad set to 7, which will cause crashing on a save game if you change it back to its default value of 5, which spINI will do. Anybody messing with uGridToLoad should know that, but Ewi was quite rash with his INIs. Half of his settings don't do anything. And then some of his settings do something not good. His INIs are like SMPC to the USKP. Unfortunately you can't just get rid of all of them, as they get embedded into your save and cause issues if removed. I see I should probably add bFloatRenderTarget to my spINI tweaks so people don't forget. Your using my Steroids version of Grass, which I think you have mistakenly thought would be better. The Steroids version is for Grass on Steroids and Verdant users. I probably should go into more detail on those tweaks in the description. Perhaps the Launcher crashing problem is due to ENB, as I just enabled the ENB dll and it took forever to work and even stopped responding for a moment, although it never crashed. So to sum up what you should do to get your INIs working: In Skyrim.ini, add in their indicated sections: [General] uGridsToLoad=7 uExterior Cell Buffer=64 uInterior Cell Buffer=32 iPreloadSizeLimit=262144000 [SaveGame] bUseSaveGameHistory=1And SkyrimPrefs.ini [Display] bFloatPointRenderTarget=1 bFull Screen=1 iSize H=1080 iSize W=1920 Then use these spINI tweaks: Anisotropic Filtering - DisabledAntialiasing - DisabledDepth of Field - DisabledGrass - Optimized grass (no steroids)Intro Sequence RemovalMap Menu - Blur RemovalMap Menu - OptimizedScreenshots DisabledShadows - ENB Optimized HighShadows - Land shadows enabledShadows - Tree Shadows enabledTutorials - DisabledDon't use any of the other tweaks. I'll see if I can't update spINI Tweaks with these.
  4. DoubleYou
    That reminds me that I need to get on the light tweaks, as those have been staring me blatantly in the face as a virtual INI goldmine.
  5. DoubleYou
    Python is only currently necessary for the MO Configurator plugin for your INI files. If you have no use for that, don't worry about it. My guess is that Python will work if you run as admin. I had that issue, and it was some kind of permissions issue that only a OS reinstall fixed.
  6. DoubleYou
    What I need to know is exactly what your backup INIs are. Could you paste their full contents in spoilers. Also, I really am concerned about this Launcher crash. If the Launcher crashes, please ensure that Skyrim\skyrim_default.ini and Skyrim\Skyrim\SkyrimPrefs.ini exists. Also, have you experienced the Launcher crashing before? If so, is there some other thing (not enb) that could be causing it to crash? Does running the SkyrimLauncher outside of the spawned process of my installer cause it to crash? Also, you might try the beta file in the Miscellaneous section to see if that behaves differently for you. Also I need to know exactly which spINI Tweaks you activated. Your papyrus settings exactly replicate the default values, which is what spINI will give you, except it won't state it explicitly in the INI, since defaults are defaults until you change them. The goal of this mod is to avoid the issues you describe, so if it causes them, I very much am interested in how that can happen.
  7. DoubleYou
    My INIs are at the default values. Any tweaks you need must be placed back into the INI files or you will fail. And you're not supposed to delete any INIs during the installation process. This will certainly make you fail. ENB will not crash the launcher. Only deleting your INIs like you're not supposed to or instructed to will crash the Skyrim Launcher.
  8. DoubleYou
    You should have told me that was the error message. I could easily have directed you to that solution. Added the following to the instructions so people don't have this issue: Please ensure that your screen resolution in the Launcher is selected correctly!
  9. DoubleYou
    The installer modifies the Skyrim_default.ini and Skyrim\Skyrim\SkyrimPrefs.ini and deletes your Skyrim.ini and SkyrimPrefs.ini files in Documents\My Games\Skyrim and then calls the SkyrimLauncher to regenerate your INI files. The only way that could cause the Skyrim Launcher to crash is if something interfered in that process and deleted the Skyrim_default.ini and/or Skyrim\Skyrim\SkyrimPrefs.ini files, like an antivirus, disk optimizer tool, or some other kind of software.
  10. DoubleYou
    Not sure about the Skyrim Launcher crash, but you should have gotten more than a SkyrimPrefs.ini in your documents folder. What version of Windows are you running and do you have the admin account enabled? As to the Tweaks crash, it sounds like you enabled conflicting tweaks, which will cause it to crash.
  11. DoubleYou
    Yes, Windows Smartscreen is a pain. It's like having two User Account Controls. I doubt I can fix this automatically. The change I made should have fixed it, but when you have the admin account enabled, normalcy gets thrown out the window.
  12. DoubleYou
    Its default value is on, but it can be disabled with one of my spINI tweaks. And the image is a random screenshot. I should change that.
  13. DoubleYou
    I think my article and my sig helped too
  14. DoubleYou
    Did you try the beta installer? It should automatically fix this issue, and if so, I'd like to push it to be the new version. See this article spINI Launcher fixes up the default INI creation system spINI Creation Kit merely cleans up the Creation Kit files spINI Tweaks contains tweaks to improve performance and improve graphics
  15. DoubleYou
    @dredd3110 Please try the spINI Installer beta file I just uploaded in the Miscellaneous section and see if that fixes the issue.
  16. DoubleYou
    Strange. Did you activate the admin account on your version of Windows? If that's the case, the INI files will be created on the admin account instead of your user account, which would cause this behavior. If that is the case, simply delete your INIs again and launch the SkyrimLauncher like normal and that would fix that. Nope, that's Oblivion. Skyrim uses Documents\My Games\Skyrim
  17. DoubleYou
    Both. Replace your profile INIs with the new ones. Then install the Tweaks.
  18. DoubleYou
    That's strange. It didn't need compatibility mode on my Windows 10 :O_o:
  19. DoubleYou
    When you say that nothing is created, where are you looking for the created INIs? They are created in Documents\My Games\Skyrim as Skyrim.ini and SkyrimPrefs.ini. Do these files not exist after the Launcher is run?
  20. DoubleYou
    Hmmm... I might be inclined to agree with you there.
  21. DoubleYou
    Mod Source: fINIp 3 (Fallout INI Project 3) by DoubleYou fINIp 3 fINIp 3 (Fallout INI Project 3) is an attempt to restore decency to the Fallout 3 INI configuration files. Sadly, Bethesda screwed up its INIs. You would think that their INI creation method via the Fallout Launcher would be completely error free, as how could they mess up what essentially is a simple text file? but it isn't. They are chock full of uh-ah-choo! sneeze-worthy lines. Enter fINIp 3. We spinned the files that Fallout 3 uses to create your presets, twirled them into a sensible order, and whirled away most of the errors. This removes a large portion of the obsolete and redundant lines that the Fallout Launcher erroneously applies to the INI files. Installation: Download the main file. Run the installer. Follow the on-screen instructions. Read any warnings carefully! Once the installer has completed, the Fallout Launcher will automatically run to generate your new INI files. If using Mod Organizer, copy the generated Fallout.ini and FalloutPrefs.ini files to your \profiles\ directory.Once this is done, please add any and all desired tweaks, as these are NOT tweaked outside of default tweaks. This mod cleans up the INI creation process. It doesn't add tweaks. Archive Invalidation will need to be redone. Uninstallation: Replace your Fallout.ini and FalloutPrefs.ini files with the backups you should have made according to the warnings in installation and go to step 3. If you neglected to heed my warnings, verify integrity of game cache and go to step 2. Run the Fallout Launcher and select your preset. If using Mod Organizer, copy the new Fallout.ini and FalloutPrefs.ini from your Documents\My Games\Fallout3 directory to your \profiles\ directory. Eat salt and vinegar chips.
  22. DoubleYou
    On a more serious note, I'll check out VR after I finally check out 3d glasses. Maybe that wasn't serious.
  23. DoubleYou
    Google Chrome auto-updates. :alien:
  24. DoubleYou
    Oh, I thought you meant my Utilities Pack... :ghostface:
  25. DoubleYou
    Could be useful for sex education.
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.

  I accept