[FUBAR-BDHR]

Reported:

http://scp.indiegames.us/mantis/view.php?id=1866

[Sololop]

Awesome! Thanks a lot.    Hope someone will find a fix for this soon.

[chief1983]

Me too, but as it isn't detrimental to gameplay it's not going on the hotlist for 3.6.10.  Hopefully for the next release though.

[ARSPR]

Hey guys, maybe this is not a bug but bad pof data. Check my note in the mantis report 1866.

Some testing should be done. (Retail vs. Media vps model, different ships...)

[chief1983]

Yeah I was just going to suggest seeing if this ever happens with retail data.

[CaptJosh]

I've still yet to see it with media VPs. Are we sure this isn't a problem with a rogue pof file or vp file somewhere?

[chief1983]

I have a feeling me and FUBAR are two of the more obsessive at keeping our stuff clean, if we've both seen it recently I'm pretty sure it's some sort of bug.  So you mean you've _only_ seen it with retail data?

[FUBAR-BDHR]

Just to clarify I haven't actually seen this I just reported it for him since he couldn't.  I thought I saw an old report in Mantis that was fixed but apparently that one was for Knossos warps only. 

[chief1983]

Must have been another bug you confirmed recently, there's so many new ones I get them confused.

[FUBAR-BDHR]

Yea that was "The Blinding White Light of Death" one.  I don't think that one made Mantis yet either. 

[CaptJosh]

I'm quite obsessive with keeping things clean myself. I don't have any extraneous items in /data or subfolders. I must admit to never having gone back to retail once I had mediaVPs to work with. I'm using the 3.6.10 VPs and the latest radar icons build I know of with a radar icons VP. Is there any particular build I should test with to see if I can find this bug?

[Sololop]

Well I am getting the bug constantly, and Im using build 5032 of 3.6.10 with no mediaVPs, and I haven't changed anything in any folders or whatever, and followed instructions carefully so I did not fail this session. I've had this since day one of my FSO experience.

[CaptJosh]

So it's retail only? How odd.

[Sololop]

So even if I'm using the FSO exe, with no mediaVPs is a retail problem? I would have thought it was still a Freespace open issue. I may have my terminology wrong.

Edit: I now do believe this bug is with the MediaVPs. More importantly, something that is included in the MV_Core.vp. Reason for this being, I copied this to a separate folder a few days ago, and forgot to delete the original, and overlooked it when I checked a bit ago.  Didn't mean to lead in the wrong direction, but the problem is there, nonetheless. So far, now that it (mvcore) is moved, the problem is gone. However by re-enabling the MediaVPs, or MV_Core, or alternate mods like blueplanet or derelict, the problem re surfaces. Every time.

I'm now going to search every nook and cranny in my FS folder to avoid further confusion in troubleshooting. 

[chief1983]

The term 'retail' is often used to describe either a retail .exe, or the retail game data (.vp's).  Normall you can get the meaning out of context, but if I just say I'm "playing retail" it could be hard to interpret what I mean.

[FUBAR-BDHR]

Might be a good time to have you run the debug build and attach the fs2_open.log from the data directory.  You only need to start the game and get to the menu then you can exit.

[WMCoolmon]

It's not a model issue. Setting the clipping plane is handled on a lower level than the rest of the graphics code. Anything that would be rendered to the right of that line, before the clipping plane was reset, just wouldn't appear in that image. Once the ship is all the way through the effect, it should be instantly removed from gameplay, rendering, and physics. Before the ship is all the way through the effect, the clipping plane should be active.

Now the model might have a bug in it that's causing the issue. But the underlying code should be rigorous enough to handle that sort of thing (Say, the bounding box being improperly set up - although the code used to use the radius rather than the bounding box). If the code is dumb enough that it's closing the warp effect before the ship is all the way through, but smart enough that it knows the ship isn't all the way through yet and doesn't remove it from gameplay, then the bug is the dumb code being used in conjunction with the smart code.

[ARSPR]

Please check mantis info...

 

I cannot reproduce the error.

[FUBAR-BDHR]

Still waiting on a log file from Sololop. 

Can anyone else reproduce this?

[WMCoolmon]

Something to consider might be the video card you're using. It might be that it doesn't properly support the clipping plane, so the effects get turned off by the FS2Open code, but the video card doesn't have any way to handle clipping the model itself. I seem to remember there being an issue with at least one older version of video card, I think it was the GF4MX440, where that would be the case.