Hard Light Productions Forums

Community Projects => The FreeSpace Upgrade Project => The FreeSpace Port Upgrade => Topic started by: Soul Reaver on October 02, 2019, 04:35:55 am

Title: Post Processing Bug with MediaVPS
Post by: Soul Reaver on October 02, 2019, 04:35:55 am
I recently reinstalled FSPort and FSPort MediaVPS using the Knossos installer.

When I tried the game, I noticed the primary weapon shots looked really bad:
https://i.imgur.com/lNrC7pR.png

Turns out this happens when I add the -post_process flag in the FSOpen options.  Removing it makes the shots look normal (but of course also removes the post processing affects from the graphics, like bloom)

The same thing happens on two different machines with totally different specs.
Is there anything I can do to fix this?
Title: Re: Post Processing Bug with MediaVPS
Post by: Nightmare on October 02, 2019, 04:43:32 am
Which built are you using? Most recent one?
Title: Re: Post Processing Bug with MediaVPS
Post by: The E on October 02, 2019, 05:56:05 am
This looks to me as if the bits in the effect texture that are supposed to be fully transparent aren't. Does this happen for this specific weapon or all weapons?

If it's only this weapon, it might be worthwhile to look at the textures for that effect and make sure that they're set up correctly.
Title: Re: Post Processing Bug with MediaVPS
Post by: Soul Reaver on October 02, 2019, 06:59:11 am
Which built are you using? Most recent one?

Whichever one gets installed via Knossos.  It lists the FSPort MediaVPS version as 3.7.2, and FSPort as 1.0.0.

This looks to me as if the bits in the effect texture that are supposed to be fully transparent aren't. Does this happen for this specific weapon or all weapons?

If it's only this weapon, it might be worthwhile to look at the textures for that effect and make sure that they're set up correctly.

It happens with both the ML-16 and the Disruptor, as you can see in the screenshot.  Not sure about others.
Title: Re: Post Processing Bug with MediaVPS
Post by: Nightmare on October 02, 2019, 12:52:59 pm
Could you try switching to the most recent built? Outdated builts often have bugs that have been fixed in the meantime.
Title: Re: Post Processing Bug with MediaVPS
Post by: Soul Reaver on October 02, 2019, 04:12:17 pm
Could you try switching to the most recent built? Outdated builts often have bugs that have been fixed in the meantime.

Can't see any way of installing a newer version using Knossos.  Unless I'm missing something?
Title: Re: Post Processing Bug with MediaVPS
Post by: The E on October 02, 2019, 04:29:54 pm
In the FSO options, switch "Preferred Engine Stability" to "Nightlies" or "Release Candidate", then update FSO and select one of the newer builds in the launch options.
Title: Re: Post Processing Bug with MediaVPS
Post by: Soul Reaver on October 02, 2019, 06:09:15 pm
T
In the FSO options, switch "Preferred Engine Stability" to "Nightlies" or "Release Candidate", then update FSO and select one of the newer builds in the launch options.
Tried FSO 19.0.0-RC1, same problem.

I also tried Freespace Port MediaVPs version 3.6.12 but had the same problem.

Is anyone else seeing the same issue when they use the post_process flag on a Knossos full install for FSPort with FSPort MediaVPS?

Title: Re: Post Processing Bug with MediaVPS
Post by: Nightmare on October 02, 2019, 07:30:08 pm
I just noticed a similar issue while checking the Morning Star (MVPs-2018, current FSO RC) in the F3 lab after using the MorningStar_Glow bitmap in a mod produced a box-like glow similar to the one in the OP. Checking the file, it appears that its base color isn't black. Don't have FSPort at hand so I can't tell whether the ML16 and the Avenger glow have the same problem, but it seems possible.
Title: Re: Post Processing Bug with MediaVPS
Post by: Soul Reaver on October 02, 2019, 11:18:47 pm
Should I try reporting this in Mantis?
Never used it before but I assume I just need to create an account.
Title: Re: Post Processing Bug with MediaVPS
Post by: Nightmare on October 03, 2019, 04:42:20 am
I don't think anybody is using Mantis anymore.
Title: Re: Post Processing Bug with MediaVPS
Post by: mjn.mixael on October 03, 2019, 08:28:29 am
These effects haven't changed in years. If this is just now coming up, I suspect engine changes or video card driver issues.
Title: Re: Post Processing Bug with MediaVPS
Post by: Nightmare on October 03, 2019, 08:42:41 am
FWIW, the Morning Star looks bizarre and completely broken in the F3 lab, but fine in-mission.
Title: Re: Post Processing Bug with MediaVPS
Post by: Soul Reaver on October 03, 2019, 04:21:31 pm
These effects haven't changed in years. If this is just now coming up, I suspect engine changes or video card driver issues.

My (admittedly uneducated) suspicion is that it's engine changes.  I've got two completely different machines that experience basically the same problem with completely different video cards (one's a crappy laptop that can barely run Freespace 2 Open, the other is gaming PC that runs it just fine).

Most likely changes haves been made to how postprocessing works that has somehow become incompatible with the FSPort MediaVPS

I haven't noticed any issues the Freespace 2 MediaVPS using postprocessing, only the FSPort ones.

It would help if more people tested it to confirm though - it's easy enough to test.  Install F2, use Knossos to install MediaVPS, FSPort and FSPort Media VPS, set FSO Options>Graphics to include Post Processing.  Start a new game and test by shooting the ML16 in the first training mission.
Compare to how it looks with post processing turned off.

Assuming this is a problem introduced through engine upgrades, is there any way for me to report it to someone who might be able to look into it and fix it?
Title: Re: Post Processing Bug with MediaVPS
Post by: MitoPL on October 04, 2019, 06:23:39 am
I'm actually pretty sure that had happened to me too back some time ago, but I'm not sure if it stopped happening at some point or if I just got used to it. I think it was being strange once I've started using some of the first PBR 3.7.2 builds?

I'm not at my PC right now, but this evening I'll open up FSO to check that out and report.
Title: Re: Post Processing Bug with MediaVPS
Post by: MitoPL on October 05, 2019, 07:50:04 pm
Alright, I'm back - sorry for the double post.

Checking the F3 lab, the problems definitely come from fsport-mediavps. The 'boxiness' issue definitely comes into both Disruptor and D-Advanced, and also Flail. Some other weapons (ML-16, Avenger, Banshee, S-Breaker) experience discoloration after I turn on the post proccessing. ML-16 and S-Breaker look like they're being massively oversaturated for some reason. Not sure how that works, though.
Title: Re: Post Processing Bug with MediaVPS
Post by: Goober5000 on October 05, 2019, 09:20:54 pm
I'm not a graphics guy, so I have no idea what could be causing this, from either an application or an art perspective.

However, I'll agree with mjn.mixael that if it was a mod-wide problem, a lot more people would have reported it in the past few years.  Can you try upgrading your graphics drivers?
Title: Re: Post Processing Bug with MediaVPS
Post by: mjn.mixael on October 05, 2019, 09:38:55 pm
Did some checking. I get the same issue on my machine in multiple mods where these same effects are used. I suspect something is bad with the images themselves. That said, I see the issue in the tech room, but not in mission. However, the Avenger bolts seem to be inverted somehow in mission.
Title: Re: Post Processing Bug with MediaVPS
Post by: Soul Reaver on October 05, 2019, 10:01:49 pm
I'm not a graphics guy, so I have no idea what could be causing this, from either an application or an art perspective.

However, I'll agree with mjn.mixael that if it was a mod-wide problem, a lot more people would have reported it in the past few years.  Can you try upgrading your graphics drivers?

As I said above, I already updated them to the latest on my gaming PC (that one has a GeForce GTX 760).  And I get the same issue on a different computer (laptop with built in graphics card) too.
It's obviously a newer problem, because I used to play FSPort a few years back and didn't notice the same thing back then.  I suspect engine changes.

I strongly suspect those images are set up in some sort way that the current post processing implementation doesn't like.
I just don't know who the right person would be to look into it and try and fix it.
Title: Re: Post Processing Bug with MediaVPS
Post by: Goober5000 on October 05, 2019, 10:32:38 pm
If I knew exactly what about the images the engine didn't like, I might be able to perform the adjustments in IrfanView or GIMP, or failing that, get Galemp to fix them.

But fixing it is the easy part; figuring out what needs fixing is the tricky part.

I'll ask on the #fsu channel on Discord; maybe someone there has an idea.
Title: Re: Post Processing Bug with MediaVPS
Post by: Goober5000 on October 05, 2019, 11:42:26 pm
Here's what Axem had to say:
Quote
i recall weapon bitmap issues before when incorrectly used dds compression was used
weapon bitmaps should use dxt1 compression with no alpha

But the Avenger, Banshee, Disruptor, and S-Breaker all had DXT1 compression with no alpha, as expected.
Title: Re: Post Processing Bug with MediaVPS
Post by: AdmiralRalwood on December 05, 2019, 06:46:10 pm
These effects haven't changed in years. If this is just now coming up, I suspect engine changes or video card driver issues.
The issue has been happening for years; while searching for something else, I stumbled across me talking about this exact issue with Axem on Discord in September of 2017 (specifically September 20th). At the time I noted that the problem occurred in builds at least as far back as 3.8.0, but not 3.7.4. No idea why a GitHub issue wasn't made; presumably I got distracted and forgot about it (I don't really play FSPort very often/ever; in fact, I think the only reason I encountered the bug myself was because I was reproducing a report somebody else made at the time).