FEEDBACK v2.0.0 - Feedback & Bug Reports

[DoubleYou]

Check the crash log from Crash Logger.

  On 4/10/2022 at 9:28 PM, ephemeraljoy said:

Hello all. I've got a repeatable instant crash to desktop when I hover over a staff in a container (chest, enemy, MY inventory). First time using the step guide, so I certainly could have done something wrong. Any thoughts? Thanks!

Expand  

 

[ephemeraljoy]

Attached the latest, but the logs all reference different staff textures in textures\carn2k4\...

Again, I'm new to this...what would you suggest from here? Reinstall the Elemental Staffs SE & Step Patch - Conflict Resolution mods?

Thanks again!

crash-2022-04-10-21-53-49.logFetching info...

[DoubleYou]

My guess is your Elemental Staffs download was corrupted. Delete the file, re-download, and reinstall. If that doesn't fix it, do the same with the Step Patch Conflict Resolution. Hopefully that will fix it. 

[Sakiri]

Ok guys I'll give those a try. 

Appreciate the help! 

[ephemeraljoy]

Thanks @DoubleYou all fixed!

[Kordac]

I completed the guide last night and everything seems to be fine from a quick test before I went to bed, the game looks fantastic and the LOD is incredible.  However DynDOLOD gave me an error when it finished.

 

Warning: Property not found mycell in scripts\ccasvsse001_doorunlockscript.pex ccasvsse001-almsivi.esm [REFR:05000F2B] (places ccASVSSE001_DoorUnlockTrig [ACTI:05000F26] in GRUP Cell Persistent Children of [CELL:040142EC] (in DLC2SolstheimWorld "Solstheim" [WRLD:04000800]) at 8,5)

 

I know that has ccasvsse001 is Ghosts of the Tribunal CC content and I can find the 05000F2B reference in xEdit but I have no idea what to do next or even if I should do anything. Is this something I need to worry about? LOOT reports the plugin as cleaned

[wolf44]

I'm not 100% sure if it's mentioned here. 

But... might be worth noting that for whatever reason Nemesis won't execute properly and kick back an error (6002 was the particular one I had received). This is due to AV, specifically the real-time scanner in windows from my experience.

I don't know if this is common knowledge or not, but might be worth noting under the Nemesis expanded section. 

Otherwise awesome guide! 

[theeternalsw0rd]

  On 4/20/2022 at 5:29 PM, wolf44 said:

I'm not 100% sure if it's mentioned here. 

But... might be worth noting that for whatever reason Nemesis won't execute properly and kick back an error (6002 was the particular one I had received). This is due to AV, specifically the real-time scanner in windows from my experience.

I don't know if this is common knowledge or not, but might be worth noting under the Nemesis expanded section. 

Otherwise awesome guide! 

Expand  

It's not just Nemesis. Any of the tools that have file output can be hit with problems due to Windows Defender (xLodgen, DynDOLOD, TexGen, etc). I had to add exceptions for the executables and the output folders to avoid sporadic issues.

[ButchDiavolo]

  On 4/20/2022 at 7:07 AM, Kordac said:

I completed the guide last night and everything seems to be fine from a quick test before I went to bed, the game looks fantastic and the LOD is incredible.  However DynDOLOD gave me an error when it finished.

 

Warning: Property not found mycell in scripts\ccasvsse001_doorunlockscript.pex ccasvsse001-almsivi.esm [REFR:05000F2B] (places ccASVSSE001_DoorUnlockTrig [ACTI:05000F26] in GRUP Cell Persistent Children of [CELL:040142EC] (in DLC2SolstheimWorld "Solstheim" [WRLD:04000800]) at 8,5)

 

I know that has ccasvsse001 is Ghosts of the Tribunal CC content and I can find the 05000F2B reference in xEdit but I have no idea what to do next or even if I should do anything. Is this something I need to worry about? LOOT reports the plugin as cleaned

Expand  

I get this error all the time as well when I re-run DynDOLOD. I also checked in SSEedit to see it could be easily fixed, but all the properties seem to be filled and no errors show up. So I guess it is a problem in the original script/ pex file. I have never been fortunate with fixing scripts in CreationKit, so I won't try to see if it is fixable that way. Maybe someone who is more script-savvy could fix it? But then again, I haven't played Almvisi yet, so I don't know if it needs to be fixed. (How is this for non-commital? )

[TechAngel85]

  On 4/24/2022 at 3:45 PM, ButchDiavolo said:

I get this error all the time as well when I re-run DynDOLOD. I also checked in SSEedit to see it could be easily fixed, but all the properties seem to be filled and no errors show up. So I guess it is a problem in the original script/ pex file. I have never been fortunate with fixing scripts in CreationKit, so I won't try to see if it is fixable that way. Maybe someone who is more script-savvy could fix it? But then again, I haven't played Almvisi yet, so I don't know if it needs to be fixed. (How is this for non-commital? )

Expand  

I've reported this to the USCCCP mod. There's 18 pages of bug reports over there, though, so it could be a while before it's addressed.

[ButchDiavolo]

  On 4/24/2022 at 4:01 PM, TechAngel85 said:

I've reported this to the USCCCP mod. There's 18 pages of bug reports over there, though, so it could be a while before it's addressed.

Expand  

Cool! Thanks, Tech   But... 18 pages of bug reports?!

[FendisKhan]

Within STEP 2:

Within SkyrimSE Installation Steps, the example file location leaves off the suggested "\Games" prefix (used in the Setup Guide)

Similarly, in the Tool Setup table (xLODGen)  the suggested "\Games" prefix is also missing.

[FendisKhan]

Still within STEP 2, the BethINI setup inclluded:

• Ensure the Mod Organizer path is correct (e.g. ..\Modding\Tools\Mod Organizer).

However, the default System Setup places the Mod Organizer directly under \Modding, rather then under Modding\Tools

[z929669]

The 'games' prefix is redundant for tools in most cases and I have removed it from the Setup Guide for consistency with other guide/mod instructions.

[FendisKhan]

BethINI Baseline Configuration:

The example image for "Detail" does not match either described option. Lens Flare is unchecked (agreeing with ENB option) yet Ambient Occlusion remains checked (disagreeing with ENB option)