Zanderat Posted September 7, 2018 Share Posted September 7, 2018 That makes no sense. How could SKSE possibly do that? Link to comment Share on other sites More sharing options...
Ethreon Posted September 7, 2018 Share Posted September 7, 2018 There might (might I say) be a problem. Some folks are reporting in other threads that after installing the new SKSE build, their game seems a bit "sped up" (overlapping dialogue and the like.) If anyone else is noticing this in their game, please let us know. Sounds like FPS over 60. Link to comment Share on other sites More sharing options...
leonardo2 Posted September 7, 2018 Share Posted September 7, 2018 "You are using a newer version of Skyrim than this version of SKSE64 supports.If this version just came out, please be patient while we update our code.In the meantime, please check http://skse.silverlock.org for updates.Do not email about this!Runtime: 1.5.50SKSE64: 2.0.7" What should I do?Even after installing, I get the same message and the new version of SKSE doesn't seem to work ... I don't know what I am missing .. :sad:That's easy to correct, provided that you have installed SKSE64 2.0.8. Just verify game cache in Steam then run the vanilla game launcher, which I did and that worked for me. :smile: Link to comment Share on other sites More sharing options...
Kulharin Posted September 7, 2018 Share Posted September 7, 2018 (edited) Hm, so what mods are going to break if I update to the new SKSE version? I didn't even know that was a thing but apparently PapyrusUtil, Quick Loot, Swift Potion will be broken if I use the new SKSE64 until the author updates those mod... In the case of Quick Loot that'll be never. So should I just opt not to update to 2.08 and use 2.07 with the old EXE like I've been doing? Any issues with that? If so what other key mods are going to need an update? Royal pain in the ass for a pointless Bethesda update Edited September 7, 2018 by Kulharin Link to comment Share on other sites More sharing options...
LeddBate Posted September 8, 2018 Share Posted September 8, 2018 I'd say that for now, staying with 2.0.7 and the previous Skyrim exe is probably your best bet for avoiding issues. Cruising the threads, the situation seems a bit muddled right now. Link to comment Share on other sites More sharing options...
Zanderat Posted September 8, 2018 Share Posted September 8, 2018 I'd say that for now, staying with 2.0.7 and the previous Skyrim exe is probably your best bet for avoiding issues. Cruising the threads, the situation seems a bit muddled right now.The only thing going on, is that while SKSE64 has been updated, most mods that need it have not. Myself, I am waiting on PapyrusUtil. Link to comment Share on other sites More sharing options...
LeddBate Posted September 9, 2018 Share Posted September 9, 2018 I'm starting to see why a significant amount of mod authors that ported their mods to SE decided to go with spells and books rather than getting an MCM menu. Link to comment Share on other sites More sharing options...
Trosski Posted September 9, 2018 Share Posted September 9, 2018 I'm trying to compile a plugin, and I am getting a LINK1181 error. it says that skse64_1_5_50.lib is missing. I have recompiled skse64 using the source code, but it won't generate the lib file. I am only getting the .dll, .iobj, .ipdb, and .pdb files. is there a step I am missing? Link to comment Share on other sites More sharing options...
Jebbalon Posted October 5, 2018 Share Posted October 5, 2018 So the first post is not updated for 2.0.8 or the latest 2.0.9 for SSE version 1.5.53anyway....My question is that in 2.0.9 the Data\Scripts folder now has 85 .pex files and the Data\Scripts\Source folder has 62 .psc files.What's new text file doesn't mention 20+ new scripts and we would kinda need the source files to make use of them.Is this error or oversight or am I just seeing things? Link to comment Share on other sites More sharing options...
Jebbalon Posted October 9, 2018 Share Posted October 9, 2018 DayDreamer got a response from SKSE team and posted on AFK mods - Here - Tried the team email, and got a reply from Ian Patterson: It looks like the build script I usually use only outputs .pex files for scripts we've modified, but the newer script that does a multithreaded build also includes .pex dependencies. They should be identical to Bethesda's other than the metadata. I'll modify the new script so it doesn't generate the extra files, but it shouldn't be causing problems. In case anyone was interested. Link to comment Share on other sites More sharing options...
Recommended Posts