Hosted Projects - FS2 Required > Between the Ashes
BtA Bug Report Thread
mjn.mixael:
OK, not counting screencam, here are all the available BtA HUDs with just $Scale_Gauges set to NO first and then YES. No other changes.
FS1
FS2 (Yes, the Myrmidon exists in BtA solely to have an unused ship to assign the FS2 HUD to so that I could have all 4 in a single mod)
UWar
Zod
And finally, the FS1 HUD circle is not distorted. I checked.
If you want to do this properly, you need to copy the Hud Guages.tbl from BTA1_Core.vp and then change the setting there and save it to BtA/data/tables
antsa:
Apparently you cannot target Spoiler:waypoints in mission 1 after you restart the mission, i tried this several times. same is with Spoiler:"The will to act" mission where i cannot seem to target the thots via key f12 after restarting the mission.
Also
in mission Spoiler:"To steal a march on" mission objective "disable transports" dont get marked as true even after disabling transports what i can. and 30min later ingame nothing happens, cannot get past that point at the moment. Great Story so far
using 3.7.4 as recommended
ps. it was kinda funny to see Spoiler:phi wing attack Antares station during civilian escort mission i dont know if that was intentional :D
mjn.mixael:
There is a known issue regarding hotkeys and multiple restarts. It's not that you can't target waypoints, it's that you can't target them with the hotkey. You can still find the waypoint using your radar and targetting it with the "target the object in my forward cone" key (defaults to Y). I'm assuming this is due to a code bug and since we were releasing on 3.7.4 (And aside from setting Hotkeys in the ships dialog in FRED, we aren't doing anything with them that people haven't done in FSO for years), it's an issue I just have to deal with. Generally restarting FSO gets the hotkeys to work again. We'll have to see if SDL helps at all in 3.7.5 when I work on compatibility there.
Spoiler:In "To Steal A March On" that objective is impossible. I would need additional information to understand where the mission stalled out for you. This mission has an 'end sequence' that starts after a certain number of ships destroyed, a certain wing arrives OR a certain amount of time has passed. From there it's a chained set of events that lead to a warp out directive. It's more or less impossible for the mission to stall out with out an SCP or other error at work preventing the timer from functioning. Regardless of how you play the mission, after 450 seconds, you will start getting messages that lead to a Warp Out directive. So yeah, I guess I need a little more info from you on this one.
I assume you mean mission 6, "Acts of Voltion", with Phi wing? I bet I know why they are doing that. I probably gave them an attack order for an invisible object near Antares to force them to use their afterburners (before we had the SEXP good-afterburn-time). How were you close of enough to Antares Station to see that? Most of that mission takes place 10-14k out from the station.
antsa:
--- Quote from: mjn.mixael on October 26, 2016, 08:31:46 am ---There is a known issue regarding hotkeys and multiple restarts. It's not that you can't target waypoints, it's that you can't target them with the hotkey. You can still find the waypoint using your radar and targetting it with the "target the object in my forward cone" key (defaults to Y). I'm assuming this is due to a code bug and since we were releasing on 3.7.4 (And aside from setting Hotkeys in the ships dialog in FRED, we aren't doing anything with them that people haven't done in FSO for years), it's an issue I just have to deal with. Generally restarting FSO gets the hotkeys to work again. We'll have to see if SDL helps at all in 3.7.5 when I work on compatibility there.
Spoiler:In "To Steal A March On" that objective is impossible. I would need additional information to understand where the mission stalled out for you. This mission has an 'end sequence' that starts after a certain number of ships destroyed, a certain wing arrives OR a certain amount of time has passed. From there it's a chained set of events that lead to a warp out directive. It's more or less impossible for the mission to stall out with out an SCP or other error at work preventing the timer from functioning. Regardless of how you play the mission, after 450 seconds, you will start getting messages that lead to a Warp Out directive. So yeah, I guess I need a little more info from you on this one.
I assume you mean mission 6, "Acts of Voltion", with Phi wing? I bet I know why they are doing that. I probably gave them an attack order for an invisible object near Antares to force them to use their afterburners (before we had the SEXP good-afterburn-time). How were you close of enough to Antares Station to see that? Most of that mission takes place 10-14k out from the station.
--- End quote ---
Oh, okay that figures it out with those hotkeys, im suprised i have not noticed that before.
Well about the phi wing, i happened to target phi 1 and its orders were to attack antares station when i stopped timewarp, so i was kinda cofused for a second there.
Spoiler:Well... i tried the mission several times with different approaches with no different outcome, last thing what anyone says is that "thats the last of the transports" or something like that when all visible transports are disabled. after that nothing happens except few wings of enemy fighters and then nothing. i dont get warp out directive, and when i leave debriefing says "this is a red alert mission so no" something like that, and of course failure from admiral or whatever.maybe i should record this thing or how else i could propably give more info about this?
mjn.mixael:
You can record it if you want. Also screenshots of the Event Log and Message Log at the point where the mission stalled would be helpful.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version