Bridge Commander Central

BC Forums => BC Technical Support => Previous "Black Screen of Death" Fixes => Topic started by: NX-73811 on January 02, 2009, 01:15:39 PM

Title: BSOD - File: ".\Scripts\Custom\NanoFXv2\NanoFX_Config.py", line 29 eFX_ParticleControl - invalid syntax
Post by: NX-73811 on January 02, 2009, 01:15:39 PM
Well, my problem is clear of the tile i think, i tried to get a console report, (to help finding the problem) but Testmode seems not to work, i tried every option in how to initiate testmode, all 3 didn't work in any way, i evenly tried to hexedit my options.cfg to have windowed mode, but that didn't work either. Here is a list of what i installed (up to that point, the problem encountered)

STBC Clean
1.1 Patch
KM 1.0
Galaxy Charts
Slipstream Drive
some minor modifications for NanoFX v2 (just gfx)
many ships
EDIT: i forgot to say, i also have got ATP1+Mleos fix (and it worked :D )
--------------------------------------------------
this is what i installed, but didn't test because of problem:
EDIT2: i also installed the "ds9 shield effect by vladko1"
          and a tactical display modification, just new shield display and Mouse Icons
NanoFX v2 Singleplayer BETA fix
Generations Ent-B Bridge

i hope this helps even without conole report

Thanks for evenly reading
Title: Re: BSOD - File: ".\Scripts\Custom\NanoFXv2\NanoFX_Config.py", line 29 eFX_ParticleControl - invalid syntax
Post by: MLeo on January 02, 2009, 03:11:07 PM
Have you tried pressing * instead of ` (which, btw, is _NOT_ ')?
Title: Re: BSOD - File: ".\Scripts\Custom\NanoFXv2\NanoFX_Config.py", line 29 eFX_ParticleControl - invalid syntax
Post by: NX-73811 on January 02, 2009, 03:14:33 PM
well, as i guessed from your instructions, you have an othe Keyboard layout than my one, i have the german layout.
on the left site of the 1 is "^", but did work for most ST games of Activsion (like EF1 and EF2) for pressing "*" i would need to make shift+"#" but i can try it

EDIT: "*" doesn't work either
EDIT2: lol i have a backup i idiot, but it would be quite interesting, what caused that BSOD
Title: Re: BSOD - File: ".\Scripts\Custom\NanoFXv2\NanoFX_Config.py", line 29 eFX_ParticleControl - invalid syntax
Post by: MLeo on January 02, 2009, 05:50:50 PM
Well, without a console report we can't tell what caused the bsod.


In case of a German layout, it should be a * (Multiply), it's possible it's the numpad version.

The ` is sometimes called the "backtick". It's different from '.
On UK keyboards it's at the '.
Title: Re: BSOD - File: ".\Scripts\Custom\NanoFXv2\NanoFX_Config.py", line 29 eFX_ParticleControl - invalid syntax
Post by: KrrKs on January 03, 2009, 07:17:14 AM
I once had a BSoD caused by one of the "newer" Nano FX fixes. But I don't know if it was the same (patch). I think it was because that patch didn't work with KM and/ or GC.
To MLeo: On German Layout Keyboard the "^" is used for the console, as NX-73811 said.
Title: Re: BSOD - File: ".\Scripts\Custom\NanoFXv2\NanoFX_Config.py", line 29 eFX_ParticleControl - invalid syntax
Post by: MLeo on January 04, 2009, 03:16:21 PM
To MLeo: On German Layout Keyboard the "^" is used for the console, as NX-73811 said.
That's not what the scripts say... But then, I don't have a German layout to test all of that. :P
Title: Re: BSOD - File: ".\Scripts\Custom\NanoFXv2\NanoFX_Config.py", line 29 eFX_ParticleControl - invalid syntax
Post by: NX-73811 on January 10, 2009, 09:30:17 AM
and here i go agin: a BSOD lol but this time i got a console report :)

(http://www.gfx-hoster.de/bild/14656/screenshot001jpgV50X0.jpg)
i hope this is helpful in helping
Title: Re: BSOD - File: ".\Scripts\Custom\NanoFXv2\NanoFX_Config.py", line 29 eFX_ParticleControl - invalid syntax
Post by: MLeo on January 10, 2009, 09:39:36 AM
Attach the file scripts/Custom/NanoFXv2/NanoFX_Config.py
Title: Re: BSOD - File: ".\Scripts\Custom\NanoFXv2\NanoFX_Config.py", line 29 eFX_ParticleControl - invalid syntax
Post by: NX-73811 on January 10, 2009, 09:44:22 AM
here it is:

Code: [Select]
TRUE = 1
FALSE = 0
###[BridgeFX Settings]###
bFX_Enabled = 1
###
bFX_ExpSparkFXLevel = 3
bFX_DamageSparkFXLevel = 3
bFX_DamageSparkFXDuration = 60.0
bFX_ParticleControl = 20
###
###[CameraFX Settings]###
cFX_Enabled = 1
###
cFX_ViewScreenDefault = 8.0
cFX_ViewScreenMax = 128.0
cFX_AwayDistance = 8.0
cFX_ForwardDistance = 8.0
###
###[ExplosionFX Settings]###
eFX_Enabled = 1
###
eFX_LightFlickerFX = "On"
eFX_FixBrightGlows = "On"
eFX_ExpSparkFXLevel = 4
eFX_DamageSparkFXLevel = 3
eFX_DamageSparkFXDuration = 60.0
eFX_DebrisFXLevel = 4
eFX_DebrisFXDuration = 30.0
eFX_ParticleControl =
eFX_RotationFX = "On"
eFX_SplashRadius = 25.0
###
###[SpecialFX Settings]###
sFX_Enabled = 1
###
sFX_AtmosphereGlowFX = "On"
sFX_PlasmaFX = "On"
###
###[WarpFX Settings]###
wFX_Enabled = 1
###
wFX_MaxRandomDistance = 30
###
Title: Re: BSOD - File: ".\Scripts\Custom\NanoFXv2\NanoFX_Config.py", line 29 eFX_ParticleControl - invalid syntax
Post by: MLeo on January 10, 2009, 09:50:44 AM
You can actually attach the file itself in this forum. ;)
And when posting code, it's usually easier to just use the code tags.

Here is the fixed version:
Code: [Select]
TRUE = 1
FALSE = 0
###[BridgeFX Settings]###
bFX_Enabled = 1
###
bFX_ExpSparkFXLevel = 3
bFX_DamageSparkFXLevel = 3
bFX_DamageSparkFXDuration = 60.0
bFX_ParticleControl = 20
###
###[CameraFX Settings]###
cFX_Enabled = 1
###
cFX_ViewScreenDefault = 8.0
cFX_ViewScreenMax = 128.0
cFX_AwayDistance = 8.0
cFX_ForwardDistance = 8.0
###
###[ExplosionFX Settings]###
eFX_Enabled = 1
###
eFX_LightFlickerFX = "On"
eFX_FixBrightGlows = "On"
eFX_ExpSparkFXLevel = 4
eFX_DamageSparkFXLevel = 3
eFX_DamageSparkFXDuration = 60.0
eFX_DebrisFXLevel = 4
eFX_DebrisFXDuration = 30.0
eFX_ParticleControl = 0
eFX_RotationFX = "On"
eFX_SplashRadius = 25.0
###
###[SpecialFX Settings]###
sFX_Enabled = 1
###
sFX_AtmosphereGlowFX = "On"
sFX_PlasmaFX = "On"
###
###[WarpFX Settings]###
wFX_Enabled = 1
###
wFX_MaxRandomDistance = 30
###
Title: Re: BSOD - File: ".\Scripts\Custom\NanoFXv2\NanoFX_Config.py", line 29 eFX_ParticleControl - invalid syntax
Post by: NX-73811 on January 10, 2009, 09:58:18 AM
thank you, worked!
and next time, i ll post correct :lol: