Project

General

Profile

Bug #13050

ModuleRCSFX's runningEffectName can only be "running"

Added by JPLRepo over 7 years ago. Updated over 7 years ago.

Status:
Closed
Severity:
Low
Assignee:
-
Category:
Plugins/Add-Ons
Target version:
Start date:
09/18/2016
% Done:

100%

Version:
Platform:
Windows
Expansion:
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

Description
The effect associated with an ModuleRCSFX can only be named running, otherwise they are constantly on and not affected by the state of the RCS.

Steps to replicate
1) edit a .cfg file of a part using ModuleRCSFX , like rcsBlockRV-105.cfg
2) rename running under EFFECTS to anything, like testeffect
3) change the line runningEffectName = running under MODULE>name = ModuleRCSFX to runningEffectName = testeffect
4) test the modified part ingame, see the fx beeing constantly on

Notes
On the ModuleEnginesFX, renaming the associated effect is working, in comparison to ModuleRCSFX. The problem described herein is especially affecting modders that are building parts with both an ModuleRCSFX as well as an ModuleEnginesFX, like the RCS Blocks of a Briz upper stage.

Tested under Windows, should affect more (any?) platform

Problem with runningEffectName being defined as private field.

error.png (368 KB) error.png visualisation of the problem, effects are constantly on when the effect node isnt named "running" InsaneDruid, 09/18/2016 11:38 AM
25548

History

#3 Updated by JPLRepo over 7 years ago

  • Status changed from New to Investigating
  • % Done changed from 0 to 20

#4 Updated by JPLRepo over 7 years ago

  • Status changed from Investigating to Confirmed
  • % Done changed from 20 to 10

#5 Updated by TriggerAu over 7 years ago

  • Category set to Plugins/Add-Ons
  • Status changed from Confirmed to Being Worked On
  • Assignee set to TriggerAu
  • % Done changed from 10 to 30

#6 Updated by JPLRepo over 7 years ago

  • Status changed from Being Worked On to Ready to Test
  • Assignee deleted (TriggerAu)
  • Target version set to 1.2.1
  • % Done changed from 30 to 80

#7 Updated by JPLRepo over 7 years ago

  • Status changed from Ready to Test to Closed
  • % Done changed from 80 to 100

Closing. Issue was resolved in KSP 1.2.1.

Also available in: Atom PDF