One small thing Sandor might want to take note of...
Quote:Mark as Unmodified
This context menu tool marks the selected record as unmodified
Could someone get away with some sneaky editing?
The Gecko would still pick it up right...
I still haven't installed it (I won't until it's had more time to be tested/until I know it has no adverse effects on large scale modding), and TBH I can survive with the current CS. It's still an admirable addition to the toolset and I'm interested in seeing how it is received.
To answer your question though, my understanding is that the CS will only ever save anything that is marked as changed. If something is marked as unchanged, that will not be saved to the ESP.
hrug:
To answer an earlier question, I believe that the user manual said something about fixing the .lip generator.
Quote:Originally posted by InsanitySorrow
DL it, seriously , Fixes some CS bugs as well as getting rid of all the complaints it makes, plus a ton of other stuff.
It depends on how you define 'complaints'.
If you refer to the errors during the loading process it makes this tool useless, unless the editor warnings are still available.
The loading errors allow me to fix, assess and review a file.
For example PG connection errors, EDID duplicates, teleport link problems, attached to wrong cell etc. etc.
Quote:Originally posted by AnImpatientFan
The Gecko would still pick it up right...
Yes.
BTW nice catch.
Quote:Quote:Originally posted by AnImpatientFan
The Gecko would still pick it up right...
Yes.
So even if I marked it as unmodified it would still save to the .esp?
If it does what I think it does, it could save some time when cleaning records in the Gecko etc.
Quote:It depends on how you define 'complaints'.
If you refer to the errors during the loading process it makes this tool useless, unless the editor warnings are still available.
The loading errors allow me to fix, assess and review a file.
For example PG connection errors, EDID duplicates, teleport link problems, attached to wrong cell etc. etc.
Instead of a pop up all the warnings are logged onto another window that is initiated on startup of the .exe.
So PG errors and all that are logged straight onto the CSE log window.
Quote:Originally posted by AnImpatientFan
Quote:Quote:Originally posted by AnImpatientFan
The Gecko would still pick it up right...
Yes.
So even if I marked it as unmodified it would still save to the .esp?
If it does what I think it does, it could save some time when cleaning records in the Gecko etc.
I meant it the other way around, I was referring to 'sneaky'.
If something gets changed the Gecko will list it.
Unchanged content won't be saved.
I don't have the tool installed but it's easy enough to test it.
Change something in an interior cell.
Then mark it as unmodified, save the esp and open it with the Gecko.
If it works as intended there's no cell change listed.
Quote:Originally posted by AnImpatientFan
Quote:It depends on how you define 'complaints'.
If you refer to the errors during the loading process it makes this tool useless, unless the editor warnings are still available.
The loading errors allow me to fix, assess and review a file.
For example PG connection errors, EDID duplicates, teleport link problems, attached to wrong cell etc. etc.
Instead of a pop up all the warnings are logged onto another window that is initiated on startup of the .exe.
So PG errors and all that are logged straight onto the CSE log window.
Great, that sounds fine.
Quote:Originally posted by sandor
Quote:Originally posted by AnImpatientFan
Quote:Quote:Originally posted by AnImpatientFan
The Gecko would still pick it up right...
Yes.
So even if I marked it as unmodified it would still save to the .esp?
If it does what I think it does, it could save some time when cleaning records in the Gecko etc.
I meant it the other way around, I was referring to 'sneaky'.
If something gets changed the Gecko will list it.
Unchanged content won't be saved.
I don't have the tool installed but it's easy enough to test it.
Change something in an interior cell.
Then mark it as unmodified, save the esp and open it with the Gecko.
If it works as intended there's no cell change listed.
I see.
Might be useful if you accidentally edit something.
Quote:Originally posted by AnImpatientFan
Quote:It depends on how you define 'complaints'.
If you refer to the errors during the loading process it makes this tool useless, unless the editor warnings are still available.
The loading errors allow me to fix, assess and review a file.
For example PG connection errors, EDID duplicates, teleport link problems, attached to wrong cell etc. etc.
Quote:
Instead of a pop up all the warnings are logged onto another window that is initiated on startup of the .exe.
So PG errors and all that are logged straight onto the CSE log window.
Great, that sounds fine.
Just like this:
I think you can filter out all the other text in the window that you don't need via preferences.
I'd love to hear more about this as you hear about it. We use OBSE anyway so it's no problem. Are they planning on listing the features, do you think or would it be worth recording things as we find them ourselves?
Nevertheless, I'm adopting TID's approach by not touching it until it's received the thumbs-up.
Many thanks to KP for alerting me. :goodjob:
Doubt it really counts for much, but I'm using it :yes:
The Lip gen is fixed, but you need to CS 1.0 EXE file inside your OB folder, plus you need to edit the CS INI to allow multiple instances of the CS. Not tried it yet though.
I should have mentioned the complaints go into a seperate window xD
Just for future link n' click handiness (since I don't see a linky for this yet) -
Here is the Bethesda RELZ thread for shademe's CSE:
http://forums.bethsoft.com/index.php?/to...-extender/
He/she has included a quick listing of the features and fixes, within the "spoiler" tags, in their OP of the above thread.
Of course, you still have to read the multi-page "README" that comes with the CS extender, to fully grasp what has changed, how, and how to use the new features.
I have not downloaded the CSE - yet. I plan to eventually, though.
Koniption