Jump to content


Photo

Exception in unit userscript line 324:


  • Please log in to reply
15 replies to this topic

#1 BlacksburgNick

BlacksburgNick

    Prisoner

  • Members
  • 11 posts

Posted 30 September 2017 - 07:09 PM

Hi All,
 
I apologize if this has already been covered, but I've searched the forums and haven't been able to find anything.  I suspect it has something to do with Large Reference data maybe?  I get the same error code even if I disable Realistic Water 2.  I tried to generate lod without Labyrinthian and the code just popped up on Japhet's Folly.  I tried leaving both off and I got it the error again anyway.  Any help would be appreciated!
 
(Also, how the heck do you hide / show text in these thing?  I tried to hide the wall of crap below here but couldn't figure out how ::(:  )
 
 
Include large blocks of text in spoiler tags like this:
 
[spoiler]
... paste your text here
[/spoiler]

Edited by Greg, 30 September 2017 - 07:35 PM.
Added spoiler tags

  • 0

#2 sheson

sheson

    Dragon Prince

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 2,522 posts

Posted 30 September 2017 - 07:23 PM

Upload entire log to a file service or use pastebin for example.
 
Is this with 2.33/2.34? If older than that, try latest version.
 
 

There may be a permission problem because of UAC or anti virus that prevents DynDOLOD.exe from spawning LODGen.exe child processes.


Edited by sheson, 30 September 2017 - 07:26 PM.

  • 0

#3 BlacksburgNick

BlacksburgNick

    Prisoner

  • Members
  • 11 posts

Posted 30 September 2017 - 07:33 PM

I have to keep beating my Avast off with a stick, it really doesn't like LODGen.exe.  I'll totally disable Avast, try again, and get back to you.  If that doesn't do it, I'll load the whole file to pastebin like you suggested.  Thanks, Sheson!


  • 0

#4 BlacksburgNick

BlacksburgNick

    Prisoner

  • Members
  • 11 posts

Posted 30 September 2017 - 09:14 PM

Greg, thanks!

 

Sheson - I had to totally uninstall Avast, but that got it done.  Even with all the shield turned off it was still causing issues for me.  To answer your previous question that i missed, I am using 2.33 DynDOLOD, 2.3 SSE resources, and I am using the Skyrim SSE beta version that has the new Survival Mode content.  I don't know if that's causing other issues.

I've got one weird thing going on still.  I keep getting a popup as follows:

--------

LODGeneratorCMD

LODGeneratorCMD has stopped working

A problem cause the program to stop working correctly.  Windows will close the program and notify you if a solution is available.

--------

 

This popup occurs a large number of times in rapid succession, but DynDOLOD generates successfully i think.  I was trying to generate 3D tree lods, but instead i get NO tree lods at all.  That being said, the original problem was solved by killing the antivirus.

 

When I get off work in a few hours I'll try to generate a non-3D lod and see what happens.


  • 0

#5 sheson

sheson

    Dragon Prince

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 2,522 posts

Posted 01 October 2017 - 03:52 AM

Check the LODGen logs in ..DynDOLOD\Logs\ for errors. If there is no meaningful message in there, bring one of the command prompt window to the front and sreenshot or copy/paste what messages were written to it.
  • 0

#6 BlacksburgNick

BlacksburgNick

    Prisoner

  • Members
  • 11 posts

Posted 01 October 2017 - 03:00 PM

Hey,

 

The Windows error keeps popping up, but I can find no reference to it in the DynDOLOD Log.  I have successfully generated the LODs, but I still have no clue what's causing the windows popup (I'm still unable to generate 3D LODs, but I figured I'd deal with that later).  I have posted my log here:

https://zerobin.net/...cQuQ4OBbhBBjcw=

 

Here is my Plugin List:
https://zerobin.net/...q8C7QJBSy6MSsw=

 

Check the LODGen logs in ..DynDOLOD\Logs\ for errors. If there is no meaningful message in there, bring one of the command prompt window to the front and sreenshot or copy/paste what messages were written to it.

What do you mean by using the command prompt?  I know how to get to it in Windows and brought it up, but I didn't see anything there.

 

 

Sorry If I'm noobing this up somehow!


  • 0

#7 sheson

sheson

    Dragon Prince

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 2,522 posts

Posted 01 October 2017 - 03:32 PM

If the spawned LODGen.exe command prompt windows have errors, static LOD has not been generated completly.

You keep mentioning some windows error. What is the message exactly?

When DynDOLOD spawn the child process LODGen.exe it has a a white text on black background command prompt window. Click the icon in the task bar to brink it to the front so you can see/screenshot the messages printed to it.

LODGen.exe also writes logfiles to ..DynDOLOD\Edit Scripts\Export\LODGen_*.txt, but exceptions will most likely not be printed to it, only the console window.
It is possible that something is preventing LODGen.exe to write these logfiles and that it is the reason of the errors.

You should also clean plugins and check them for errors in xEdit.
  • 0

#8 BlacksburgNick

BlacksburgNick

    Prisoner

  • Members
  • 11 posts

Posted 01 October 2017 - 05:46 PM

Huh, Interesting.  The command prompt window definitely didn't open on it's own, that's why I was confused.  The error window that pops up is shown here:

https://imgur.com/rvohVRn

 

I'll go double check my plugins.  Thanks again for all your help, you're the man!

 

p.s.

Just for the record, my wife says If I try to give you our first born, she's getting an axe.  I didn't ask for further clarification on that statement.


  • 0

#9 BlacksburgNick

BlacksburgNick

    Prisoner

  • Members
  • 11 posts

Posted 01 October 2017 - 07:02 PM

So, i stripped out my plugins list down to some bare minimums and I'm finally catching the command prompt popping up.  I have no idea why I wouldn't see it before, but i believe this is what you were looking for:

https://imgur.com/ZE278JF

 

Here is my Log:

https://zerobin.net/...TAj4qUM6qTDoXI=

 

Thanks again!


  • 0

#10 sheson

sheson

    Dragon Prince

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 2,522 posts

Posted 02 October 2017 - 04:01 AM

That's it.

Check if deleting all files from ..DynDOLOD\Edit Scripts\DynDOLOD\cache\ before running DynDOLOD helps.

If that does not help, see if you can scroll the text back up to show what happened before the error.
  • 0

#11 BlacksburgNick

BlacksburgNick

    Prisoner

  • Members
  • 11 posts

Posted 02 October 2017 - 08:15 AM

That's it.

Check if deleting all files from ..DynDOLOD\Edit Scripts\DynDOLOD\cache\ before running DynDOLOD helps.

If that does not help, see if you can scroll the text back up to show what happened before the error.

I'm at work until 1700 EST, but I'll try this at home this evening and post after that.  Thanks again!


  • 0

#12 sheson

sheson

    Dragon Prince

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 2,522 posts

Posted 02 October 2017 - 02:36 PM

What version of MO are you using?


  • 0

#13 BlacksburgNick

BlacksburgNick

    Prisoner

  • Members
  • 11 posts

Posted 02 October 2017 - 05:05 PM

What version of MO are you using?

I'm using M02 2.0.7. 

 

I just deleted everything in DynDOLOD\Edit Scripts\DynDOLOD\cache\ and I'm going to run it again.


Edited by BlacksburgNick, 02 October 2017 - 05:08 PM.

  • 0

#14 sheson

sheson

    Dragon Prince

  • Mod Authors
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 2,522 posts

Posted 02 October 2017 - 05:16 PM

You should probably use the latest version from the fork found at https://github.com/L...anizer/releases as this bug has not been fixed in the original version, but it was fixed in the fork.

Edited by sheson, 02 October 2017 - 05:19 PM.

  • 0

#15 BlacksburgNick

BlacksburgNick

    Prisoner

  • Members
  • 11 posts

Posted 02 October 2017 - 05:39 PM

You should probably use the latest version from the fork found at https://github.com/L...anizer/releases as this bug has not been fixed in the original version, but it was fixed in the fork.

Understood.  I will try it there and report back!  Thanks for the help!


  • 0


0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users