I just wish this came out in 07 when I still had some motivation in me, this is excellent!

Err I'm feeling thick headed here.

The instructions say:

So no. 2 - do you mean the original CS.exe? Because this is not version 1 - at least not be documentation ... it is version 4.0

This exe - is that the lame.exe - rename it to TESConstructionSetOld.exe ... if so why if one is loading via the OBSE loader.

If not then what is and where does the lame.exe go.

thanks

What? No. lame.exe is something else entirely; it's used by CSE but you're not supposed to rename it. Those are the instructions for getting the lip synching function to work (the v1.2 update of the CS broke it) by installing the original CS (as in, v1.0, where the lip synch worked) and renaming it as TESConstructionSetOld.exe.

Construction Set v1.0 means the original TESCS. You only need to worry about step 2 at all if you need to generate lip files for voiced dialogue.

lame.exe goes where the rest of CSE's files go. It should end up in the same folder as Oblivion.exe. Lame.exe is an mp3 encoding utility.

OK very glad I asked - thought that does not make the readme clear at all.

Without reference to that issue I can see how those who don't know would make this mistake - as in wait what exe?

thanks

What's not to get? It plainly says that you need "Construction Set v1.0's executable" - why would you assume it meant lame.exe?

Suggestion for future update: When duplicating a placed reference in the render window, can we get that to also copy the enable parent settings? The CS currently copies things like the disabled flag, but it never copies the enable parents.

Also, are any more things from the original wish list topic being planned for later?

The only two places that the lame.exe are mentioned in the rtf readme is in the uninstall section and under tools used. Not explaining what it is for.

It seems odd that there would be instructions for that without background as to why that isn't a footnote. It reads like this "to start using this, back up a version of the CS that you don't even own."

I don't live with my nose in the CS and I certainly haven't written a wiki about it - I've never even owned CS version 1 - having bought the GOTY version as my first and only purchase of Oblivion (version 1.2).

Further I asked a question to clarify and got the answer - just giving feedback that to someone not so 'in the know' the instructions for installing were a bit confusing.

All that is why. And whether these reasons are sufficient and reasonable for you - they are me.

1. The water fix was kinda iffy to begin with. I'll see if I can reproduce your issue on my end.
2. Were there a lot of warnings dumped to the console during loading ? Hiding the console should help speed up things in that case.

Please elaborate.


The amount of commands parsed is irrelevant. Did the crashes stop after removing NifSE ?


Look above.

Done.

Fixed, thanks.

Glad you finally have CSE installed

I'll look into it.

Fixed, thanks.


Well, there are now

Added to the scroll. And yes - I haven't forgotten about your LOD-centric ramblings

I suspect that Brendan means the problems mentioned http://cs.elderscrolls.com/constwiki/index.php/Landscape_LOD_Tutorial.

So how about adding http://cs.elderscrolls.com/constwiki/index.php/The_Elder_Scrolls_Construction_Set to the readme to avoid any potential questions, like "where to get or what is this thing"?

Edit: Removed the "offensive" part. The point of my reply was to suggest to add the link in the readme, not to teach you, Psymon.

Go ShadeMe! You're making the impossible come true. I'm trying this as soon as OBSE 20 gets out of beta.

For all I know you already did it, but would it be possible to hack the CS to have fully-resizable columns and windows (or maybe read the same data in brand new forms)? Trying to read 30-characters-long IDs in 5-characters-wide columns was never my definition of fun.

Now if only Beth would get the idea to provide the source to their tools, basic documentation for their file formats, and maybe part of the game engine in a .dll with source just like Civ IV (and soon V)... We could have this level of custom tools a few months after release instead of a few years.

Nice reply there.

Yes of course why didn't I open up google and start searching for previous versions of the exe that I wasn't even sure was being referenced. Man I'm stupid - thank you so much for going out of your way to not only provide a link for that but also to correct me on even stating that it might not be clear what is being stated on the basic install section. How incredibly daft of me to think that I could figure out an install without using google and relying on the readme. But thanks to you and others who I'm sure can't wait to go on correcting me on this issue that is all crystal clear. Yes why didn't I just use google instead of asking in the relz thread for a bit of clarity.

Thankfully I've paved the way on this issue and it really doesn't need to be gone over again.

I see. Thanks for the link.

Unfortunately this can't be done easily. The CS makes heavy use of the Win32 API in its interface code, which doesn't support control docking.

For what it's worth - The readMe clearly states 'Construction Set v1.0' in its header, under the requirements subheading. I expect the user to know enough to find and install the plugin's prerequisites correctly. I don't see how the instructions can be any clearer. There aren't any links to the CS v1.0 for the same reason there aren't links to the latest Oblivion Patch or OBSE - They are bound to become broken or outdated over time.

All said and done, I'm glad you finally have it set up correctly.

I might have missed it if it's here, but would it be possible to include a button in the script editor to automatically reformat the indentation of an existing script?

You have created the "Devils tool." Now what you do with it from here on forward will show you're merit & worth.

Just Curious: What if... a esp tries to load and has a mile long descripppppppptttttiooo.error. nnn

Wishlist feature: would it be possible to teach CS to recognize and compile '\n' in strings into '0Ah' newline symbol? Oblivion itself allows to format multi-lined messageboxes, but there's no way for CS to describe them, so you have to manually hex-edit the .esp if you want to format your text. Allowing CS itself to do it would make things much easier.

Does a similar project for Morrowind CS exist?

Added to the scroll.

Please clarify.

OBSE allows line breaks to be added to message(box) strings. This plugin cannot be ported to TES3 CS due to technical limitations.

Type this into the description box of an esp and try opening the editor.

wtffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff

Crash. with CSE

Before, the CS would only complain about a long description.


EDIT: and Pluggy 132 does need to be uninstalled for me to get the CSE to work also.

Well yes, but at the time i first tried using CSE I had 11 obse plugins installed.


I removed all of them except Construction Set Extender.dll and slowly added them back, testing the CS after each one. The last one I added back was pluggy, so I assumed that was the problem until I read haamas post. I then went back and tried removing each dll individually, checking the more *complex* ones first.

Removing any of NifSE.dll, OBGEv2.dll, OBSE_Elys_Pluggy.dll and CSE worked fine. Removing all dlls except these and it would also work fine.

So, yeah, I have no idea whats going on.

Thanks.


Neither do I. I'll keep an eye out nevertheless.

Consider yourself lucky. Everyone I've ever known who has used the CS to edit the description field has ended up with a corrupt ESP for their efforts. CSE did you a favor by crashing, your ESP should still be in one piece.

Small annoyance with the new script editor - if a script won't compile and you press "save and save plugin" the script window will close without saving the script or warning you that it intends to close the script editor.

I'm unable to reproduce this on my end. Could you walk me through it?