Hard Light Productions Forums
Community Projects => The FreeSpace Upgrade Project => Topic started by: Macfie on July 16, 2009, 11:17:01 am
-
I've noted a problem with all the support ships. They have no engine glows. I've seen it with the 3.6.10 RC3 and with the nightly builds. It doesn't matter what mod I'm using or which support ship. These appear to be the only ships affected. I mantised it. Issue 234. At first I thought it was a model problem but it would appear to be something in the source code. Has anyone else had this problem? I'm using an Nvidia G120 card on a quad 4 processor with windows vista.
-
I can confirm this. I thought it was mod specific so I didn't really take note, but I just went through a training mission in retail and the support ship didn't have any.
EDIT: When I said retail I meant mediavps.
-
This happens with both media VPs, FS1 Port and Retail?
If someone can confirm all three then it's definitely code.
-
It definitely happens with media VPs and the port. I don't know if I can run retail any more but I'll check.
-
I simply meant with retail data, i.e with No Mods.
-
Retail has engine glows.
-
I actually ran retail as well as no mods and both have engine glows for the support ships.
-
Then someone has buggered up the media VP models and this isn't a code error.
I'll send this over to the FSUP forum.
-
noted.
-
Solved.
It apperantly was caused by thruster glows not being assigned to subsystem.
I have fixed it in less than minute.
[attachment deleted by MSC
-
Could you do the FS1 support also?
-
Where do these files go? I have no clue...
-
.pof == model, so \freespace2\mediavps\data\models . Create the directory when necessary.
-
On a semi-related note, does anyone know why with the mvps selected, support ships don't send the messages they usually do ("Rearming complete sir, you're good to go!")?
-
.pof == model, so \freespace2\mediavps\data\models . Create the directory when necessary.
Hmmm. I did exactly as you said, yet the results are the same in the first mission of the regular fs2 campaign. Is anyone else still having problems or is just me?
Actually I played some missions in Derelict and it seems to be working, so maybe its just that particular mission mentioned above.
-
I put the files in the model folders and tried it but still no engine glows. Tried the media VPs and several mods but no engine glows.
-
Worked for me.
-
Well I can confirm it is not working in the first and second mission of the fs2 campaign. I'll check a little bit more but there seems to be a problem.
-
I put the files in the model folders and tried it but still no engine glows. Tried the media VPs and several mods but no engine glows.
The mission in Derelict had the support ships transporting maras to the arcadia station, so they were already there and I didn't have to call them in. Those had engine glows. The following mission I called the support ship in and it didn't have any, so its not working for me either.
What's weird is if you hit F3 from main hall and pick the Hygeia then hit render options and check "show thrusters" it works. Maybe it doesn't work in missions where you call it in. I'm only guessing so who knows.
-
Wasn't there a similar problem in some of the previous 3.6.10 builds where any ship that warped in after the mission start had no thrusters?
-
Wasn't there a similar problem in some of the previous 3.6.10 builds where any ship that warped in after the mission start had no thrusters?
Yes, one of the earlier builds I used had that problem.
-
So long as there are no oddities in the code, I went ahead and corrected the models.
http://www.hard-light.net/mantis/view.php?id=258
I'll post the credits to Dragon, even though I did not use the supplied models,
-
Dragon's fix did not solve the problem. See previous posts after his "fix". So if the fix is based on what he did, the problem is not fixed. I'm not sure why Instead of "$engine_subsystem=Engine", thruster details are simply called "Thruster" would cause the problem. All the Fighter and bomber models are simply called thruster and they work.
-
In fact, I just corrected the only thing that seemed to me as an issue in .pofs .
If it doesn't work, then it's most likely something worse than simple .pof error.
I'm currently working on a custom support ship for my mod (made from .pof that had only docking point), so I will check if it have thruster glows.
Also, I will check UEF support ship from BP.
-
The reason that Dragon's "fix" did not work is because in properties he put "$engine_subsystem=Engine" not "$engine_subsystem=$engine" as it should be.
And I have tested them in game, and my fix works.
[attachment deleted by MSC
-
I tried it and it didn't work for me. Hmmm..... :confused:
-
The reason that Dragon's "fix" did not work is because in properties he put "$engine_subsystem=Engine" not "$engine_subsystem=$engine" as it should be.
And I have tested them in game, and my fix works.
So did you call the support ship in? It didn't work for me.
-
I should doube-check everything that PCS2 autonamer offers to me.
Unfortunately it seems to be some more serious issue, thrusterglow is also missing on UEF support ship, I haven't checked my own jet, but it's likely that it will have the same issue.
Thruster on UEF support ship is normally visible in F3 lab, but it's missing when support is called in-mission.
-
Odd, it works fine if the ship is already present in a mission but when it is called into a mission, the glows disappear...
-
Also, $engine_subsystem=Engine is the default auto-fill by PCS and is the correct entry.
However, neither that nor $engine_subsystem=$engine or even having absolutely nothing at all (as all of the player ships are set) have any effect.
I'm baffled. But fiddling with the POF is not resolving the issue.
SCP Mantis: http://scp.indiegames.us/mantis/view.php?id=1968
FSU Mantis: http://www.hard-light.net/mantis/view.php?id=258