[Fixed]Bodyslide Zap Issue - BaseShape Dissapears

[ToxicKin]

EDIT: The issue was "fixed" within a few hours. The solution can be seen later in this thread, here. For now, the behaviour is still unexplained though.

 

Hello!

 

I'm the author of the Tera Armor CBA Bodyslide - TBBP + Zaps extension mod (which I was planning to update today), and have an issue with one of the armors behaving weirdly when I apply (new) zap sliders to it.

 

The armor in question is the Voidmeld Cuirass, which consists of 6 armor meshes, named Highelf_F and body1-body5. The issue surrounds the armor mesh "body2", and the BaseShape character body mesh.

 

What happens is that when I apply all of my new zap sliders (MainBottom, MidriffL, MidriffR, BraL and BraR) the BaseShape dissapears, despite not a single one of these zap sliders is touching it! However, when I apply my old "Main" zap slider - which simply removed the entire body2 mesh - the BaseShape shows up again.

 

Btw, the new zap sliders should, all together, create the same result as the old one: removing the body2 mesh. The reason why I added them was to increase customability.

 

Here's some pictures to further describe the problem. I also attached a 7zip archive containing the relevant files - install it and you should be able to see it in BodySlide under the "CBAdvanced TERA Armors HDT Collection Test" group.

 

All (related) zaps unticked:

 

All except the old one and one of the new ones ticked. It doesn't matter which of the new ones are unticked, the result is the same:

 

Here's the actual issue, when all new zaps are ticked, the BaseShape dissapears:

 

The two last pictures are basically the same, but proves that the old zap restores the BaseShape body mesh whether having all new ones ticked or not.

 

Does someone recognize this issue, and if so, could provide some help? I can probably redo this part of the work, but it would be great to know why this happened in the first place.

 

Thank you for your time

TERA Bodyslide Issue (2).7z

[goner01]

not sure if this is the problem but happened to me with one conversion, did you mask the part you wanted to zap and then inverted the mask? i forgot to invert it once, and it zapped everything  except what i wanted to get zapped

 

 

[ToxicKin]

not sure if this is the problem but happened to me with one conversion, did you mask the part you wanted to zap and then inverted the mask? i forgot to invert it once, and it zapped everything  except what i wanted to get zapped

 

I've actually cleared the slider data in all the new sliders once, while having the BaseShape active, just to make sure. As seen, it didn't have an effect :/ Also, in the sliderset you can actually see that all the new sliders only target the "body2" mesh, so this shouldn't be the issue.

 

Thanks for you input though

[goner01]

would have tried to take a look but can't open the file, neither in Bodyslide does it show up correctly, nor can i load it in Outfit Studio ("Failed to create project from slider set file!")

[ToxicKin]

would have tried to take a look but can't open the file, neither in Bodyslide does it show up correctly, nor can i load it in Outfit Studio ("Failed to create project from slider set file!")

 

Hmm, that is odd. Wait... Do you have ChronoTrigger's CT77Body installed? I don't think it should be a requirement, but I did use it to create the BaseShapes.

 

EDIT: Whoops, did a mistake when exporting it out of BodySlide. To get it to work, you have to open up BodySlide\SliderSets\CBATeraArmorSldTest.xml and edit out 'CBATeraArmorsData\' from the line '<SetFolder>CBATeraArmorsData\TERACBBEVoidmeldCuirassCBAHDTTest</SetFolder>'.

 

Or, alternatively, you could create a folder inside ShapeData called "CBATeraArmorsData", but, well, that's a bit odd. I'll fix this in the OP-file.

 

Either way, this was just an issue with the testing It did not solve the actual issue...

 

EDIT2: File in OP updated.

[goner01]

couldn't see anything wrong maybe one of the problems currently still happening with BS/OS? (export problem, since in OS itself the zaps seem to be all correctly connected)

 

have you tried to remove some ZAP sliders and exporting it with a few less?

[ToxicKin]

couldn't see anything wrong maybe one of the problems currently still happening with BS/OS? (export problem, since in OS itself the zaps seem to be all correctly connected)

 

have you tried to remove some ZAP sliders and exporting it with a few less?

 

I am afraid I don't understand what you mean - or I might do, but then I don't understand how it would help with the problem

[goner01]

 

couldn't see anything wrong maybe one of the problems currently still happening with BS/OS? (export problem, since in OS itself the zaps seem to be all correctly connected)

 

have you tried to remove some ZAP sliders and exporting it with a few less?

 

I am afraid I don't understand what you mean - or I might do, but then I don't understand how it would help with the problem

 

 

well as far as a i know OS still has a few problems during exportiing, at least sometimes.

what i noticed so far is the more sliders i have for an outfit the more prone it is to make trouble during export (corrupting some of the bsd files)

 

so it would just be a test if that particular slider works correctly if you export it with fewer zap sliders, if it should work with fewer sliders, then i think the only workaround atm is to use fewer sliders until the new version of BS/OS comes out.

 

again not sure it that is exactly the problem, but it might be worth a try

[ToxicKin]

 

well as far as a i know OS still has a few problems during exportiing, at least sometimes.

what i noticed so far is the more sliders i have for an outfit the more prone it is to make trouble during export (corrupting some of the bsd files)

 

so it would just be a test if that particular slider works correctly if you export it with fewer zap sliders, if it should work with fewer sliders, then i think the only workaround atm is to use fewer sliders until the new version of BS/OS comes out.

 

again not sure it that is exactly the problem, but it might be worth a try

 

 

I suppose I should give it a shot, though the thing is... All the zaps work wonderfully by themselves. It's just when I enable all of the new ones that the BaseShape dissapears. Still, I'll redo them and see what happens. Thanks for your help, I'll come back shortly.

[ToxicKin]

Alright, the issue is actually solved! Whoo!

 

Now, the solution didn't seem to be what you, dachande, proposed. Sure, it would surely have worked, but what really made Bodyslide unhappy, was how I had set up some of my zap sliders.

 

I'll try to explain the fix:

 

The zaps were set up very close to each other, but I had found a good line that made a smooth curve, so it would look good even if only one of the zaps were active. Now, the issue with this, is that it left quite a few edges untouched: I selected verticies in such a way that after you've zapped two adjecent areas, there were no polygons left inbetween; however, there was still quite a few edges "leftover" instead, so to speak.

 

So, solution was simply to make the zap areas overlap, and as such all the prevous edges were removed.

 

The reason why it became angry, I think, was due to some calculation error or rendering error, as it tried to render a mesh (body2) without polygons. The mesh wasn't gone - there were still verticies attached to it! - so it didn't skip it in the rendering process.

 

Though I'm still wondering why the BaseShape dissapeared, as it's some really weird behaviour. Maybe someone else can answer why this happened? Also, should we notify Caliente and who-more-it-now-was-that-was-working-on-Bodyslide? It's not a critical bug, but likely not too hard to fix.

[ousnius]

 

Though I'm still wondering why the BaseShape dissapeared, as it's some really weird behaviour. Maybe someone else can answer why this happened? Also, should we notify Caliente and who-more-it-now-was-that-was-working-on-Bodyslide? It's not a critical bug, but likely not too hard to fix.

 

Me.

 

And I have no clue what went wrong in rendering vertices/edges/faces/zapped things/doublezappedthingsthatoverlayeachotherordont. 

 

EDIT: If you want to, you can type a descriptive bug entry for the Google code page: https://code.google.com/p/bodyslide/issues/entry

So I can take a look at it at some time.

[goner01]

Glad you got it working, and as i said wasnt sure if it might be the problem but if it did lead to a solution all good

 

 

[ToxicKin]

 

 

Though I'm still wondering why the BaseShape dissapeared, as it's some really weird behaviour. Maybe someone else can answer why this happened? Also, should we notify Caliente and who-more-it-now-was-that-was-working-on-Bodyslide? It's not a critical bug, but likely not too hard to fix.

 

Me.

 

And I have no clue what went wrong in rendering vertices/edges/faces/zapped things/doublezappedthingsthatoverlayeachotherordont. 

 

EDIT: If you want to, you can type a descriptive bug entry for the Google code page: https://code.google.com/p/bodyslide/issues/entry

So I can take a look at it at some time.

 

 

Ah, cell was it! Alright, I will send in a bug entry

 

EDIT: Entry... sent!