Author Topic: Post Processing Bug with MediaVPS  (Read 647 times)

0 Members and 1 Guest are viewing this topic.

Offline Goober5000

  • HLP Loremaster
  • Administrator
  • 214
    • Goober5000 Productions
Re: Post Processing Bug with MediaVPS
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.

  

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: Post Processing Bug with MediaVPS
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).
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.