View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001979 | FSSCP | models | public | 2009-08-21 14:51 | 2009-10-01 15:22 |
| Reporter | Macfie | Assigned To | Goober5000 | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 3.6.11 | ||||
| Summary | 0001979: Not using proper models in FSPort | ||||
| Description | I just noticed a problem. I was playing an FSPort campaign and noticed that the GTSC Faustus #medical, GTT Elysium #medical, GTFR Chronos #medical and the TAC 1#medical do not have the proper textures. They use the standard texture rather than the medical white and blue. If I go back to using the 3.6.10 build everything is normal. Went back and checked different builds. The windows 5207 build works but the windows 5219 build doesn't. I believe 3.6.10 is built off the 5209 build. So something changed in the 5219 build caused the problem. | ||||
| Additional Information | I also found that the medical ship problem also effects all of the nameplated orion destroyers in the FSPort. Instead of using the fsport model for the destroyer it just uses the standard orion model. In looking at the models affected it appears that anything beyond the basic model is being ignored. The models affected all have additional information. I.E. capital01a.pof or capital01-Soyakaze.pof in both cases it defaults to capital01.pof The same thing with the medical ships the GTSC Faustis#medical uses model science01-medical.pof but it defaults to science01.pof | ||||
| Tags | No tags attached. | ||||
|
|
You're only playing the missions? You're not doing anything to them with FRED when testing the revisions? |
|
|
This is a known and deliberate issue, and it's only there because the feature that it wants to use hasn't been enabled yet. Use 3.6.10 final, or wait until it's been included in the 3.6.11 code. |
|
|
FS Port content issue. FS Port is using features which aren't yet coded in - not-really-a-bug... |
|
|
Yes I'm only playing the missions. I'm not sure what you mean that FSPort is using features that aren't coded in yet since it works with 3.6.10. I am however working on FSCRP campaigns that could be impacted. It appears that something has been changed in 3.6.11 that makes it incompatible with the FSPort. |
|
|
Nope.. 3.6.11 has nothing changed in that regards. FS Port is just using tags which enable certain table features to activate if a build marked as 3.6.11 or higher is in use (and trunk builds are such). However the planned feature is still as of know unfinished which leads to this issue. Marking this as confirmed - feel free to close if you think this is content issue in FS Port. |
|
|
What Galemp and Wanderer said. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2009-08-21 14:51 | Macfie | New Issue | |
| 2009-08-21 15:32 | karajorma | Note Added: 0011141 | |
| 2009-08-21 17:10 | Galemp | Note Added: 0011142 | |
| 2009-08-21 17:19 | Wanderer | Note Added: 0011143 | |
| 2009-08-21 22:44 | Macfie | Note Added: 0011145 | |
| 2009-08-23 09:38 | Wanderer | Note Added: 0011151 | |
| 2009-08-23 09:38 | Wanderer | Status | new => confirmed |
| 2009-10-01 15:22 | Goober5000 | Note Added: 0011203 | |
| 2009-10-01 15:22 | Goober5000 | Assigned To | => Goober5000 |
| 2009-10-01 15:22 | Goober5000 | Status | confirmed => closed |
| 2009-10-01 15:22 | Goober5000 | Resolution | open => no change required |
