Jump to content


Photo

good ol' access violation


  • Please log in to reply
7 replies to this topic

#1 jdsmith2816

jdsmith2816

    Jarl

  • Pack Authors
  • PipPipPipPipPipPipPipPipPip
  • 850 posts

Posted 29 September 2017 - 06:01 PM

When starting TexGen for SSE it proceeds for a while and then fails with accessviolation in texgen64.  If I keep clicking the ok button it eventually states that load order is messed up due to trying to find a file id higher than files loaded.

 

My DynDOLOD is not in a privileged directory, I have no anti virus running and my UAC is disabled.  I have also attempted to run it as administrator just for ***** and giggles.

 

Any idea what could be happening?


Edited by jdsmith2816, 29 September 2017 - 06:01 PM.

  • 0

#2 sheson

sheson

    Dragon Prince

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 2,522 posts

Posted 29 September 2017 - 06:12 PM

Are you sure you are using the latest version 2.32? We troubleshooted similar errors here http://forum.step-pr...rder-messed-up/ and the fixes went into that version.

 

Test if x86 TexGen.exe starts with same problem or works.

 

See if the latest test version from this post changes anything. Simply rename DynDOLOD.exe to TexGen.exe or DynDOLODx64.exe to TexGenx64.exe.

 

Post the log ..DynDOLOD\Logs\TexGen_SSE_log.txt


  • 0

#3 jdsmith2816

jdsmith2816

    Jarl

  • Pack Authors
  • PipPipPipPipPipPipPipPipPip
  • 850 posts

Posted 29 September 2017 - 06:21 PM

The test version that you linked worked for texgen but is giving me the below error during initial load before showing the usual dialog window:

 

[00:00:11.246] Exception in unit  line -1: Error in unit 'lodgenalt' on line 81 : Not enough parameters


Edited by jdsmith2816, 29 September 2017 - 06:26 PM.

  • 0

#4 sheson

sheson

    Dragon Prince

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 2,522 posts

Posted 29 September 2017 - 06:29 PM

Make sure all files in the DynDOLOD standalone installation are from the latest version 2.32, these error indicate older versions of some files are still around.

 

Maybe delete entire folder and just copy everything new form archive.


  • 0

#5 jdsmith2816

jdsmith2816

    Jarl

  • Pack Authors
  • PipPipPipPipPipPipPipPipPip
  • 850 posts

Posted 29 September 2017 - 06:36 PM

How awkward... thanks again.  I always delete the folder when updating not sure what went sideways here. 


  • 0

#6 jdsmith2816

jdsmith2816

    Jarl

  • Pack Authors
  • PipPipPipPipPipPipPipPipPip
  • 850 posts

Posted 29 September 2017 - 07:46 PM

Hmm, so with the fresh DDL installed it keeps failing near the end of the process after around 10m stating that there were errors.  I'm not seeing the errors in the log unless I simply don't know what I'm looking for... which is quite possible.

 

https://www.dropbox....v9/log.txt?dl=0

 

Going to try with that test version with debug=1 to see if that produces anything useful.


Edited by jdsmith2816, 29 September 2017 - 07:57 PM.

  • 0

#7 jdsmith2816

jdsmith2816

    Jarl

  • Pack Authors
  • PipPipPipPipPipPipPipPipPip
  • 850 posts

Posted 29 September 2017 - 08:15 PM

Alright... using the test version with debug=1 allowed for successful generation.


  • 0

#8 sheson

sheson

    Dragon Prince

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 2,522 posts

Posted 30 September 2017 - 03:42 AM

Great to know. I will push a new version with the update from the test version soon.


  • 0


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users