| View Issue Details [ Jump to Notes ] [ Related Changesets ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0002912 | FSSCP | multiplayer | public | 2013-08-27 21:49 | 2014-02-21 07:05 | ||||
| Reporter | HalcyonY2K | ||||||||
| Assigned To | karajorma | ||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||
| Status | resolved | Resolution | fixed | ||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | 3.6.16 | |||||||
| Summary | 0002912: Hud-set-max-targeting-range SEXP for Multiplayer | ||||||||
| Description | When creating multiplayer missions, the SEXP "Hud-set-max-targeting-range" will limit the radar range on the fighter flown by the server but it won't limit any client connected to the server. The client end ships continue to operate with radar range up to infiniti. | ||||||||
| Steps To Reproduce | Add "Hud-set-max-targeting-range" on any multiplayer mission. Observe that it only limits the fighter played by the server and that the client machines are not affected by the limitation. | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files |
| ||||||||
 Relationships |
|
 Relationships |
| Notes |
|
|
karajorma (administrator) 2013-08-29 03:27 |
I've just fixed the problem, but it seems to me that the SEXP really should have another optional parameter so that you can specify which player is affected. Right now you give the command and everyone is affected in the same way. |
|
karajorma (administrator) 2013-08-29 03:33 |
Fix committed to trunk@9750. |
|
karajorma (administrator) 2013-08-29 03:34 |
I'll close this properly once I add the extra parameter I mentioned earlier. |
|
karajorma (administrator) 2014-02-21 07:04 |
Since I've decided to make that extra parameter something that a lot more SEXPs can use, there's no need to half-arse it for this SEXP. |
| Notes |
| Related Changesets |
|||
|
fs2open: trunk r9750
Timestamp: 2013-08-29 03:46:51 Author: karajorma Ported: N/A [ Details ] [ Diff ] |
Fix Mantis 2912 (Hud-set-max-targeting-range doesn't work on multiplayer clients). | ||
| mod - /trunk/fs2_open/code/parse/sexp.cpp | [ Diff ] [ File ] | ||
| Related Changesets |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2013-08-27 21:49 | HalcyonY2K | New Issue | |
| 2013-08-29 03:19 | karajorma | Assigned To | => karajorma |
| 2013-08-29 03:19 | karajorma | Status | new => assigned |
| 2013-08-29 03:27 | karajorma | Note Added: 0015246 | |
| 2013-08-29 03:33 | karajorma | Changeset attached | => fs2open trunk r9750 |
| 2013-08-29 03:33 | karajorma | Note Added: 0015247 | |
| 2013-08-29 03:33 | karajorma | Status | assigned => resolved |
| 2013-08-29 03:33 | karajorma | Resolution | open => fixed |
| 2013-08-29 03:34 | karajorma | Note Added: 0015248 | |
| 2013-08-29 03:34 | karajorma | Status | resolved => feedback |
| 2013-08-29 03:34 | karajorma | Resolution | fixed => reopened |
| 2013-09-28 17:55 | Goober5000 | Project | wxFRED => FSSCP |
| 2013-12-03 07:21 | Echelon9 | Category | => multiplayer |
| 2014-02-21 07:04 | karajorma | Note Added: 0015627 | |
| 2014-02-21 07:05 | karajorma | Status | feedback => resolved |
| 2014-02-21 07:05 | karajorma | Fixed in Version | => 3.6.16 |
| 2014-02-21 07:05 | karajorma | Resolution | reopened => fixed |
| Issue History |