Author Topic: FSPort bomb error  (Read 710 times)

0 Members and 1 Guest are viewing this topic.

Offline CT27

  • 210
I was playing the main FS1 campaign via FSPort 3.5 (with MediaVPs 2014) on a nightly from October.


I played the mission where you're trying to get people to help the Vasudan scientist refugees from Altair.  The GTSC Rosetta comes in and then two transports come in to get scientists from the Rosetta.  The mission plays fine for the most part. 
There is one minor issue I noticed though.  When the waves of Shaitan bombers come in to attack the Rosetta and launch bombs...the bombs look like Shivan bombs in the game and in the targeting box picture in the lower left corner of the screen.  The issue is that right above the targeting box, the label is "Tsunami" which is of course the name of an allied bomb.

It's a very minor issue, but is it possible to fix?

 

Offline Novachen

  • 29
  • The one and only capella supernova
    • Twitter
Actually i was never sure if this is really a bug.

Because all missiles exists as a Shivan version aswell.

The Bombers in the said mission are using "Tsunami#Shivan" for example, to be precise.

Aswell the Shivans are using #Shivan editions of the Phoenix V, Interceptor and Hornet very much for example during the campaign.
Female FreeSpace 2 pilot since 1999.
Global moderator in the German FreeSpace Galaxy Forum.

Responsible for the german translation project FreiRaum - FreeSpace auf Deutsch.
Also responsible for the Nova Upgrade Project, which upgrades and fix older campaigns to make them play- and solveable again with current builds and MediaVPs.

Release List:
German Translations:
Awakenings, Between the Ashes 1, Deneb III, FreeSpace 2 (in development), FreeSpace Port, Silent Threat: Reborn & The Destiny of Peace

Nova Upgrades:
A Walk in the Sun, Into the Halls of Valhalla, Luyten Civil War, Renegade Resurgence, Rogues!, Storm Front Saga, The Deuterium Connection, Venice Mirror & What If: Another Great War

 

Offline 0rph3u5

  • 211
  • Can we have a better version of this conversation?
    • Steam
    • Twitter
Originally they were carrying Tsunami's in FS1; the Shivans never had their own Missiles, with the notable exception of the "Unknown Bomb" and "Unknown Megabomb", until the 3.6.9 (?) MediaVPs.

The "Unknown Bomb" and "Unknown Megabomb" that exist in the FS1-tables (and so in the FS-Port tables) are actually special issue weapons for mission without shields when a stray blast would have killed or crippled your fighter.
- The "Unknown Bomb" has next to no blast radius (5 for full damage, 30 for half)
- The "Unknown Megabomb" has an unusually large half damage radius (450) but doesn't have the subsystem damage modifier other bombs have.
« Last Edit: April 29, 2018, 07:58:53 am by 0rph3u5 »
"When you work with water, you have to know and respect it. When you labour to subdue it, you have to understand that one day it may rise up and turn all your labours into nothing. For what is water, which seeks to make all things level, which has no taste or colour of its own, but a liquid form of Nothing?" - Graham Swift, Waterland

"As you sought to steal a kingdom for yourself, so must you do again, a thousand times over. For a theft, a true theft, must be practiced to be earned." - The terms of Nysa's curse, Pathfinder: Kingmaker

"...because they are not Dragons."

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
It's a very minor issue, but is it possible to fix?
Is it possible? Sure; modify the tables so that Shivan version isn't named "Tsunami" anymore. Of course, since the name is how it's identified in missions and default loadouts, you also need to change the ship tables and every mission that refers to "Tsunami#Shivan"... so it's not a simple change, but it's possible.

EDIT: I forgot about Alt Name, which would probably work much easier.
« Last Edit: April 29, 2018, 09:16:36 pm by AdmiralRalwood »
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.