View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002251 | FSSCP | tables | public | 2010-07-07 13:51 | 2012-12-18 19:42 |
| Reporter | Fury | Assigned To | Zacam | ||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | closed | Resolution | not fixable | ||
| Product Version | 3.6.12 RC3 | ||||
| Summary | 0002251: $Shockwave name doesn't work properly in 3.6.12 | ||||
| Description | mediavps 3.6.10 uses $Shockwave name: shockwave01 in all bombs in mv_assets-wep.tbm. This means that all bombs use 2D shockwaves even if 3D shockwave launcher flag is used. This worked in 3.6.10 but not in in 3.6.12, in .12 all bombs use 3D shockwaves even if $Shockwave name: shockwave01 is set. Testing is simple, just load up mediavps 3.6.10 as mod and compare bomb shockwaves in FSO .10 and .12 when 3D shockwaves flag is enabled. | ||||
| Tags | No tags attached. | ||||
|
|
This is a MediaVP problem and therefore should be in the MediaVP Mantis. http://www.hard-light.net/mantis/ |
|
|
Reported here: http://www.hard-light.net/mantis/view.php?id=571 |
|
|
...And reopening due to reading comprehension fail. >.< |
|
|
Modification of issue: Shockwave Name: does set for the 2D effect to take place, even when "Use 3D Shockwave" is on. Unless the bomb in question is shot down, at which point it uses the 3D. (Edit: It does so, because no arm time is specified on retail weapons and all weapons are considered un-armed and use dinky explosion and shockwaves instead of what's specified in either "Shockwave Name:" or "Shockwave Model:") Shouldn't it use the specified shockwave in all cases except where "Dinky Shockwave" is used (which is not applicable to Retail FS2 weapons)? |
|
|
So the issue is that '$Shockwave name:' should override '-Enable 3D shockwaves' in all cases where the weapon might spawn a shockwave? That makes sense to me. Confirm or deny and I'll come up with test data for this ticket. |
|
|
There is no way to define a 3D specific over-ride in a 2D system without enabling the 3D Shockwave option, which is set to over-ride (as it is supposed to) the 2D effect. Arguably, .10 was broken in not enforcing the flag over-ride. Note: 2D effect specified will play for when the bomb get's shot down vs. impact detonation with target. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2010-07-07 13:51 | Fury | New Issue | |
| 2010-07-07 23:18 | Goober5000 | Note Added: 0012199 | |
| 2010-07-07 23:18 | Goober5000 | Assigned To | => Goober5000 |
| 2010-07-07 23:18 | Goober5000 | Status | new => closed |
| 2010-07-07 23:18 | Goober5000 | Resolution | open => no change required |
| 2010-07-08 05:43 | Goober5000 | Note Added: 0012201 | |
| 2010-07-08 06:09 | Goober5000 | Note Added: 0012202 | |
| 2010-07-08 06:09 | Goober5000 | Assigned To | Goober5000 => |
| 2010-07-08 06:09 | Goober5000 | Status | closed => feedback |
| 2010-07-08 06:09 | Goober5000 | Resolution | no change required => open |
| 2010-07-08 06:44 | Zacam | Note Added: 0012203 | |
| 2010-07-21 04:42 | Zacam | Note Edited: 0012203 | |
| 2012-12-18 03:53 | MjnMixael | Note Added: 0014506 | |
| 2012-12-18 19:42 | Zacam | Note Added: 0014520 | |
| 2012-12-18 19:42 | Zacam | Status | feedback => closed |
| 2012-12-18 19:42 | Zacam | Assigned To | => Zacam |
| 2012-12-18 19:42 | Zacam | Resolution | open => not fixable |
