• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

MSFS error in light fx attachpoints

Messages
665
Country
us-northcarolina
I have an old dc3..(only one that has a Piedmont texture) for my private airport ...that has the light installed but do not show up on the aircraft and I was trying to correct (make worse) the situation and I keep getting this error msg.. Any help would be appreciated... maybe going about wrong..

[lights]
//by Nick
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing, 6=taxi, 7=recognition, 8=wing, 9=logo, 10=cabin
light.0 = 1, 0.00; -11.51; 4.21, fx_beacon.fx ,
light.1 = 5 -5.54; 0.42; -0.61, LIGHT_ASOBO_Landing.fx
light.2 = 5 5.53; 0.43; -0.61, LIGHT_ASOBO_Landing.fx
light.3 = 3, -3.46; 0.85; -1.25, fx_navwhi.fx,
light.4 = 3, 3.46; 0.85; -1.25, fx_navgre.fx ,



BobM.
 

Attachments

  • exterior lights.JPG
    exterior lights.JPG
    163.5 KB · Views: 119
  • changing fx in attachments for lights.JPG
    changing fx in attachments for lights.JPG
    207.1 KB · Views: 128
  • x to mdl error.JPG
    x to mdl error.JPG
    575.8 KB · Views: 99
Hi,

Did you try if a shorter attach point name or a name without a dot solves the error?
 
Hi,

Did you try if a shorter attach point name or a name without a dot solves the error? I was thinking for asobos to see it..the fx name and the one on the official folder have to match..Am I on the right path. get tried of typing this stuff over and over..lol and then seeing "red"
Thanks Arno
No but what would you recommend....
 

Attachments

  • Light0.JPG
    Light0.JPG
    189.3 KB · Views: 103
  • Light3.JPG
    Light3.JPG
    196 KB · Views: 96
Just type another name that does not have a dot in it and is less long.
 
ok..will give it a try..just the attachpointe name? I don't see a dot? doesn't the name and the line in the aircraft have to be the same...say "light.1 = 5 -5.54; 0.42; -0.61, LIGHT_ASOBO_Landing.fx

this were the problem is? change this to Landing.fx ( I see the dot there )
 
Last edited:
The attach points you show in the editor are not coming from the cfg file are they? I assume you added some attach point there yourself.

I suspect it's the .fx in the name that's part of the problem.
 
It seems to be working now. I just noticed that the .fx is removed when i recompile the mdl.. The name I changed to (under general) attachpt_fx_beacon_1.. Now in the aircraft cfg.. I use that name at the end of the line. Hope the light shows up..Noobie at this.
The fx names are coming from the official folder-fs-base effects legacy/effects folder etc..
Thanks,
BobM.
 
Hi,

I don't think you need to add an attachpoint and add the light in the aircraft.cfg file. One of the two should be enough to get a light.

I just did a small test here and for sure it is the dot in the attachpoint name in MCX. You have something like attachpt_fx_navwhi.fx_Light_03 for the attachpoint name in one of the screenshots. Why did you name it like that? Just give it a funtional name without repeating the effect file in the name. Something like light_left or light03 should be enough.
 
ok..thanks..yeah I just discovered it was period....so I removed it from effect..took off .fx and it compiled..no red..... Thanks arno..hopefully the dc3 lights will show..lol..getting too old for all this..lol

I downloaded a dc3 and in the light section..it was like this: so I modified mine and still no luck unless its something with the mdl or texture cfg or the texture file. At a loss...

; LEGACY
; Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
;-light.0 = 3, -27.20, -46.30, 0.65, fx_navredm , ;
;-light.1 = 3, -27.20, 46.30, 0.65, fx_navgrem , ;
;-light.2 = 3, -64.00, 0.00, 2.72, fx_navwhi , ;
;-light.3 = 1, -36.80, 0.00, 6.25, fx_beaconh , ;
; light.4 = 4, -6.50, 0.00, 4.80, fx_vclighth,
;-light.5 = 4, -33.00, 0.00, 4.20, fx_vclighth, ;
; MODERN
lightdef.0 = Type:3#Index:0#LocalPosition:-27.20,-46.30,0.65#LocalRotation:0,0,0#EffectFile:LIGHT_ASOBO_NavigationRed#Node:#PotentiometerIndex:1#EmMesh:LIGHT_ASOBO_NavigationRed ;
lightdef.1 = Type:3#Index:0#LocalPosition:-27.20,46.30,0.65#LocalRotation:0,0,0#EffectFile:LIGHT_ASOBO_NavigationGreen#Node:#PotentiometerIndex:1#EmMesh:LIGHT_ASOBO_NavigationGreen ;
lightdef.2 = Type:3#Index:0#LocalPosition:-64.00,0.00,2.72#LocalRotation:0,0,0#EffectFile:LIGHT_ASOBO_NavigationWhite#Node:#PotentiometerIndex:1#EmMesh:LIGHT_ASOBO_NavigationWhite ;
lightdef.3 = Type:1#Index:0#LocalPosition:-36.80,0.00,6.25#LocalRotation:0,0,0#EffectFile:LIGHT_ASOBO_BeaconTop_POS#Node:#PotentiometerIndex:1#EmMesh:LIGHT_ASOBO_BeaconTop_POS ;
lightdef.5 = Type:4#Index:0#LocalPosition:-33.00,0.00,4.20#LocalRotation:0,0,0#EffectFile:LIGHT_ASOBO_CabinBounceLarge#Node:#PotentiometerIndex:1#EmMesh:LIGHT_ASOBO_CabinBounceLarge ;



Greets
 
Last edited:
Back
Top