I am using the construction set ( with the OBSE, v20, and the OBSE extender ) and every so often I get the following error:

Microsoft Visual C++ Debug LibraryDebug Assertion Failed!Program: D:\TES4\Oblivion\TESConstructionSet.exeFile: f:\dd\vctools\crt_bld\self_x86\crt\src\vsprint.cLine: 244Expression: ("Buffer too small", 0)

After which, CS crashes, and I have to reload CS, reload the mod, reload the script, and try something else.

Now I can do:

  set dSightBonus to dNightEye

or

  set dSightBonus to SaePvarQ.pLightLevel

without getting an error.

but if I do

  set dSightBonus to (dNightEye * SaePvarQ.pLightLevel)

I get the error mentioned above.

This is very frustrating. Other times this has happened, I would rearrange the code and the problem goes away. But for this script, the code is as tight and efficient as can be!

The only other thing I can think of is that maybe the script is too long? The error kicks in on line 291, out of 294. And I still have another 50-100 lines that need to be inserted.

If anyone can shed some light on this subject, I would be very grateful. My modding has come to a complete halt over this.

saebel

Assuming you were talking about CSE when you said 'OBSE extender', does the error crop up when using the vanilla script editor, i.e., when CSE's not loaded ?

Hi, yes I meant CSE, sorry, was a wee bit frustrated.

I've tried it with the extender and without. I also upgraded the extender, but that didn't seem to help much.

I think it's the length of the script. If I break the script up into smaller chunks, like under 255 lines, even though I get errors and the script doesn't compile, at least CS doesn't crash. It may also be a character count rather than a line count I suppose, because in the example I mentioned above, it wasn't the line count but the line itself. And I was able to get that same line of code to save later by moving things around and figuring out ways to take chunks out of the code and throw them into smaller called functions. But it's really annoying, cause I still haven't got the code down to that "magic number" where the main script will save yet.

The only other thing I can think of is that maybe some of my variables should be shorts instead of floats or vice versa, but I don't think that's it.

Seems like it might be a bug in OBSE/vanilla CS. Could you PM me the plugin and the script text, along with the instructions to reproduce the issue ?

ok, will do. I was in the middle of messing with it when I read this, so I need to clean it up so that it will correctly missfire, so to speak. Thanks for offering to take a look-see. I really appreciate it.

Problem solved, thanks to shadeMe. If anyone reads this and is wondering, it was a bad OBSE plugin. Specifically one that I had created as an experiment which failed, and completely forgot that it was there. Removed bad plugin, problem went away.

Thanks shadeMe!