Open FireWolf700 opened 1 year ago
Thanks for report
Interesting, as log-wise everything seems to work fine, at least to moment of hooking everything. App/ Calibrations: v1.08.1 - does that means you play on ER version that is 1.08.1? Mod was created and play-tested on 1.09.1, therefore previous versions might not work. Are you playing with Full Screen screen mode? Could you try to start mod without any other mods running, just to figure if this is compatibility issue? Is eldenring_title_skip.dll from Skip the intro logos and remove white startup screen
Thx
Mod was created and play-tested on 1.09.1, therefore previous versions might not work.
Funnily enough, my friend is also running 1.08.1, and the mod does seem to work flawlessly for them (after a few tries of getting it to show up). So it seems a likely cause, but not definite.
Are you playing with Full Screen screen mode?
I am playing with Borderless Windowed. I'll test with Fullscreen enabled instead.
Could you try to start mod without any other mods running, just to figure if this is compatibility issue?
I will see if I can test that.
Is eldenring_title_skip.dll from...
Custom dll build by Chainfailure (from the general FromSoft modding discord, ?ServerName?). It isn't public yet (I don't think), but I did try some attempts without that dll loaded, and unfortunately the same crashes continued. I had my friend load that particular dll as well, in combination with this mod, and it didn't cause any CTDs for them.
Actually playing on borderless should cause less issues :)
If issue won't be resolved while launching mod alone, then that could be a bigger issue which I might not be capable of resolving right now, due to lack of logs in places where it crashes. Technically, you could try to debug it yourself if you are familiar with Visual Studio, but if not, then I might have to make some special version that could acquire more information about potential issue you are experiencing.
So, after a bit more testing, I can confirm that swapping to/ from Fullscreen does not solve the crashes, and neither does setting ModEngine 2 to use a blank mod folder. Currently rather dumbfounded as to what could be causing this...
EDIT: To respond to your recent comment, perhaps a more extensive logging/ information gathering version would be best? I'm unsure how to proceed, myself - and have no experience with VS.
Sure, for now unfortunately I have no solution, but will try to create slightly more debug version, that could be capable of logging a lot more extensively then right now, sorry for trouble. I am also assuming that you have not edited anything inside .ini file. Perhaps something with directX12 is causing issue, but that is just blindly guessing ideas, most likely have to have more logs
Late response here, apologies, but correct - other than enabling logs, I haven't changed anything else within the .ini file. For now, I'll remain patient and wait for further updates/ developments. Best of luck, mate, and if I can help in any way with testing, I'd be glad to assist :D
Hey, I made second release: 0.2.0 You can check out if you still have crash. In case you still have it, there is new debug version that aims at creating more logs, so you can check it out and send debug version of logs. Thx
So, unfortunately, both the regular 0.2.0 and Debug 0.2.0 still do not work... but differently.
The ModLog is from the regular 0.2.0 with logging enabled, and it will still CTD at the main menu. Other than that, not much changes.
On the other hand, the Debug .dll won't even load, according to Mod Loader. Upon starting the game, I get a "PostureBarMod.dll will not load... " popup. The game will not CTD, and the ModLog won't even change.
On an incredibly confusing success note - on using the regular 0.2.0, and simply disabling the logging feature... the CTDs stop.
Either that or repetitive re-launching of the game finally allowed it to work, but considering it now works flawlessly on the attempt that I disabled logging for the hell of it? No idea what's going on there, but at the very least, I'm incredibly happy that it works.
EDIT: Or not, it has returned to CTDing on launch, with or without logging enabled :(
Ok, that is interesting that debug version would not work at all, I will send you special version that still do a lot of logging, but might pass Loader, hopefully. It is indeed weird how it worked one time.... . In that case it would seem like issue might not have 100% reproducibility. Also I have made mod try to activate after 10 seconds in this special version, maybe more time for ER to load is somehow a thing that could help here. BTW, remember to use 0.2.0 .ini file, there was a little change made between 0.1.0 and 0.2.0 PostureBarMod.zip
Apologies for the long time to respond, I wanted to make sure that things are working as they should be. CTDs with that particular Debug version that you have sent me are far less prevalent, though IIRC when I disabled the "logging" feature, the game would not start properly. I assume this is just a result of the Debug version, as using it normally (with logging enabled, and nothing else disabled other than the control UI) has resulted in a much more CTD-free experience, if I get them at all.
Thank you for helping me so far, I can't wait to see where this project goes in the future :D
PostureModLog.txt
Windows 10 (Latest, afaik) App/ Calibrations: v1.08.1 Seamless Co-op: v1.4.3 Elden Mod Loader: v3.2 Latest version of ModEngine 2 Custom mod files (map, reg.bin, models) on top for personal overhaul project The only other DLL being loaded is eldenring_title_skip.dll