Low res objects show up in game even though removed with GECK

[miguick]

I resaved the file in GECK after cleaning, it's still 2,033 bytes in size. No change there. No new data in FNVEdit. They're simple references so it's not like there was much that could've gone differently, but i still don't see what the problem is.

[Purr4me]

Try the procedure on DantheGeeks underground hide out and play the mod or read the problems associated with it.

see what takes place. Learn from it, me telling anything will just get rebutted.

 

Disputes are worthless in this regard. Been there already, done that already...but you need to see it your self and I know dam well no one will take heed.

 

That's ok with me..BTW, contacting the devs is useless any way, been there too.

 

Old history brings up things we are not allowed to talk about here, I've been instructed directly by an admin from here NOT too. let it go.

 

Or do the procedures or read the complaints. I don't care if you don't.

[miguick]

Ok, Underground Hideout, I see where you mention that vortex room stuff. I'll give it a whirl when I have time and try to discern what xEdit could be doing to it, maybe it's something tangible that can be corrected in the program or the procedure. Thank you for your time.

[Purr4me]

Ok, Underground Hideout, I see where you mention that vortex room stuff. I'll give it a whirl when I have time and try to discern what xEdit could be doing to it, maybe it's something tangible that can be corrected in the program or the procedure. Thank you for your time.

The reason I posted there in the first place is becasue I trouble shot these things and found out what the user had done. The user followed instructions and was able to save his game.

 

and as I am thinking about it? I believe I had him or her send my that plugin so I could verify the issue.

 

But. I am not here to put down the tool, that is NOT what this is about, the other poster brought all of this up, not me. I said a i don't care.

it's simple, it's short, and it 's sweet...just start over and be done with it.

 

This issue was here long before New Vegas came into the light.. and it has NEVER changed. today Nov 28th 2016 and it still there.

I enjoy helping people out, not arguing results found many many years as we go. I watched them re-code with in hours a version just to allow a single "Element" to process in the tool !

 

By the time the new version hit, the mod in question was removed. "there was some questionably concern about an entry" something like that said on the dev site.

I'm not blind. I am not ignorant either.

 

Things said to me as if I was a child is so dam demeaning it isn't funny.

I am still here trying to help with out stepping on toes.

 

THEY HAVE BIG FEET !!!

[Purr4me]

here (https://postimg.org/gallery/1dcgbqpi/) procedure to remove the treat completely from the tool.

 

I made this long ago.

 

So it is very out dated too ,I said it was along time ago. and the versions show the dates, with some other things for what ever reason I uploaded there, it's just there.

 

it's up to the user to decide but I offer for conscious reasons.

 

Caution, always check from time to time on these settings as they do change for one reason or another.

 

you'd think some one would modify the gecks' scripts and I don't mean power ups. but that wishful thinking.

Edited November 29, 2016 by Purr4me

[RoyBatterian]

Yes I read the forums, and yes I know how to use the tools properly. That's neither here nor there. I am not attacking you personally missy, I question the information you post and don't get all condescending with me please.

 

"Vortex from hell" as you put it is caused by references exceeding the havok bounds of a cell. It IS caused by objects, usually movable statics, being outside of the havok bounds of a cell. That bounds is ~27000 units in any direction. It can be caused by any object though. If you then disable the object the effect will occur because havok is trying to act on a object which is not loaded. Yes xEdit should not have z -30000 in it at all and I've reported it to zilav many times that this is bad in the Fallout engines. This can be triggered too by bad weather meshes from a certain mod I won't mention having a size exceeding 24000 in all directions.

 

miguick, thanks for performing that test. It's fairly obvious that when a form is deleted all it's data is removed, and when set to disabled that data is reinserted because it would cause a crash if it was completely absent. Just disabling those forms in geck and saving a plugin will probably produce one of the same size.

[Purr4me]

Wait for (miguick) to complete 4 hours of play time under these conditions before responding.

 

If you informed them? why have none of them responded to the issue ,why are we still subjected to fixing mods so made this way?

 

Lost cause is your argument if you know already and if you know already, what I post is confirmation we have been left in the dark.

 

So just wait, be patient. the facts are already posted on the hide outs thread which makes any statement by you here Null.

 

:wallbash: that's all your doing, wasting time here. besides, I'm enjoying your video so just wait...ok :mad:

[Purr4me]

had a post and then a power out here in town. lost it all

[Purr4me]

All (miguick) needs is a valid vortex result to complete the Identification of this issue.

 

To undue the vortex Prior to entering the reactor room..a hard saved game there and enter verify the activity is present is then load in xedit, expand trees and file all the "Undeleted entries made" simply remove the "Opposite to parent entries" and save the plugin, load it in game and enter the room.

 

all activity will now be gone. But he must produce the flawed plugin to see the results and the instructions so given here.

 

-z300000 will be omitted and left in place. DLC's "masters" on the other hand area different story.

 

but a screen shot is all that is required this task has been completed. even a saved game file for me is enough.

 

regardless of the out come, this data came from only one place where it should not be coming from in the first place.

 

Yes xEdit should not have z -30000 in it at all and I've reported it to zilav many times that this is bad in the Fallout engines. This can be triggered too by bad weather meshes from a certain mod I won't mention having a size exceeding 24000 in all directions.

Ya think ? 28th of nov 2016 it is, how long has this been going on?

 

yeah sure. You can use any version of choice and come out the same way every time.

 

The real killer here is I used 313 on Fo4 mod authors mod to repair things properly...BUT ! I did not clean the file, I did download his updated package and saw again a file size change from what I did...he cleaned it and still responds as I rebuilt it. Lucky devil until some one complains that is?

 

So, not all records are Decoded after all this time...up and left this game? been along for the ride the whole journey and still this Decoding has stagnated.

 

Accident prone Programing.

Edited November 29, 2016 by Purr4me

[RoyBatterian]

They have been informed, and zilav has already admitted it is not safe in these engines. He says these engines are "fragile" and that is a direct quote. This issue is easy to reproduce, repeatedly, without fail. Basically this stuff doesn't happen in Skyrim or Oblivion. Which is the games they care about and know, so they need reliable information from sources they trust before they will act upon it.

 

Setting something to disabled and setting the enable state to opposite of player is also wrong. You cannot have an enable parent and set something disabled. GECK will complain about this too if you try to do it, it is an invalid combination of flags and enable parents.

 

You cannot disable tree's which have tree LOD or the game will instantly crash to desktop. Also easy to reproduce.

 

You cannot disable MSTT (which are moveable statics), and have them -30000, this will also cause the vortex. Enable parenting them is fine (but not with -30000), the vanilla games do it all the time. Changing them to x markers is not a good thing to do either, but it doesn't harm anything either, I still wouldn't recommend it.

 

No, not all records are decoded fully, it doesn't mean the information is stripped from the plugins.

 

Accident prone programming? If you provide proof of things instead of just complaining about it endlessly they will fix it. Providing proof is giving them plugins which reproduce the error in a reliable manner, not just pointing them to a forum post.

 

Enjoy the show.