View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000593 | FSSCP | mediaVP | public | 2005-10-17 00:24 | 2005-10-19 02:19 |
| Reporter | WMCoolmon | Assigned To | taylor | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | resolved | Resolution | fixed | ||
| Summary | 0000593: fighter2t-03 error | ||||
| Description | Warning: Couldn't open texture 'THRUSTER01' referenced by model 'fighter2t-03.pof' | ||||
| Tags | No tags attached. | ||||
|
|
Change the case of "thruster" to lowercase. I have no idea why this is an issue on Windows with it's case insensitivity and all, but that's the problem. And obviously the game does actually find the texture for thruster01 even when it throws the error, as it appears on the ship in-mission. edited on: 10-17-05 02:53 |
|
|
Actually this is a problem with file location. The thruster graphics are effects but this is trying to load it as a texture map and those are restricted to the data/maps/ directory. If you put a copy of thruster01 in data/maps/ then it should work without issue. I do this in my custom VPs. |
|
|
That makes sense, but there's more to it than that. This map is used on just about every Terran ship below transport class, yet this warning only actually appears for the HTL Perseus. Furthermore, just changing the case of the map to lowercase actually does remove that warning. Is there some hard-coded exception (if ( texture_name=="thruster01" ) { load from effects }) or something that's causing this to happen? |
|
|
Yes it does check for "thruster" as lowercase but it's not supposed to load thruster graphics so the name check is to skip loading. Since the requested image is uppercase then it tries to load it as a texture which it can't do since it's not in data/maps/. I just left it that way in my VPs in case it was some model thing. I guess it's worth fixing for real though. I'm making changes to force all names to lowercase so we'll see if that helps or hurts anything. Should get rid of the message at the least. |
|
|
Ok, try it with the next public build. If it doesn't break anything then I'll resolve this. It worked ok for me but with my custom VPs I don't think that should be the final word on the fix. edited on: 10-17-05 12:40 |
|
|
Looks good. I think this is resolved. |
|
|
Fixered. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2005-10-17 00:24 | WMCoolmon | New Issue | |
| 2005-10-17 00:25 | WMCoolmon | Status | new => assigned |
| 2005-10-17 00:25 | WMCoolmon | Assigned To | => WMCoolmon |
| 2005-10-17 06:51 | StratComm | Note Added: 0003578 | |
| 2005-10-17 06:52 | StratComm | Note Edited: 0003578 | |
| 2005-10-17 06:53 | StratComm | Note Edited: 0003578 | |
| 2005-10-17 11:37 | taylor | Note Added: 0003580 | |
| 2005-10-17 13:15 | StratComm | Note Added: 0003581 | |
| 2005-10-17 13:33 | taylor | Note Added: 0003582 | |
| 2005-10-17 13:33 | taylor | Assigned To | WMCoolmon => taylor |
| 2005-10-17 16:39 | taylor | Note Added: 0003583 | |
| 2005-10-17 16:40 | taylor | Note Edited: 0003583 | |
| 2005-10-19 02:10 | StratComm | Note Added: 0003592 | |
| 2005-10-19 02:19 | taylor | Status | assigned => resolved |
| 2005-10-19 02:19 | taylor | Resolution | open => fixed |
| 2005-10-19 02:19 | taylor | Note Added: 0003593 |
