Surface "-1" doesn't get my runway invisible

That's my SCASM code:
Header( 1 42.8214 42.5714 23.5429 23.2929 )

LatRange( 42.5714 42.8214 )

Copyright( " [Version 2.6 Build 62]" )




Area( 5 42:41:47.0544 023:25:05.1113 30 )
LayerCall( :rwy 24 )
Jump( : )
:rwy
RunwayData( 42:41:47.0544 023:25:05.1113
Alt 530.9
Heading 94.7
Length 11811
Width 148
Id 09
Markers 0
Lights 16;C
Surface -1
Threshold 0
ThrOffN 0
ThrOffF 0
ExtN 0
ExtF 0
ThrLightsN 69
ThrLightsF 01
AprLN 10
AprLF 09
VasiBarsN 88
VasiSpaceN 200
VasiDistN 4990
VasiSideN 120
VasiSlopeN 3
VasiBarsF 88
VasiSpaceF 200
VasiDistF 4990
VasiSideF 120
VasiSlopeF 3
)
EndA
Unfortunately i'm still having a visible runway (sort of).. See picture below



Does somebody know where i might be doing wrong?
 
I'm having the same problem with the one I am trying to put together, though mine is not as complex in information as yours. All I have is the following:

=====================================

;Grand Central Air Terminal, Glendale, CA
;Circa 1957-1959

Header( 0 34.00 35.00 -118.00 -119.00 )
LatRange( 35.00 34.00 )

Area( 5 34.153666757 -118.281166703 24 )
LayerCall( :rwy 24 )
Jump( : )

:rwy

RunwayData( 34.151460041 -118.280839633
Alt 166.116
Heading 319.15
Length 3650
Width 100
Markers 00
Lights 2
Surface -1

Threshold 0

ThrOffN 0
ThrOffF 0

ExtN 0
ExtF 0

ThrLightsN 01

;AprLN 10
;VasiBarsN 8
;VasiSpaceN 0
;VasiDistN 5000
;VasiSideN 153
;VasiSlopeN 3.0

ThrLightsF 01

;AprLF 09
;VasiBarsF 8
;VasiSpaceF 0
;VasiDistF 3627
;VasiSideF 153
;VasiSlopeF 3.3

)
Return
EndA

=====================================

I have "commented-out" the things I don't need and changed the code values to reflect the runway at Glendale, but to no avail. I'm getting the exact same picture with the ".r8" concrete value.

If I use the "1" instead of "-1" for the surface type I get another form of concrete ".r8" texture. Rather strange. I even reinstalled the Silver Wings textures for the FS9 install and nothing. I'm hoping I don't have to reinstall the whole thing. Next step would be to copy over the textures from the original CD's and reinstall Silver Wings again.

Strange since this worked well about a month ago with a Carswell AFB / Texas '62 project I'm helping out with. No issues whatsoever.

Could it be the effect of a Win7 update that we're not aware of?
 
Okay, I've re-installed the ".r8" textures from the CD's and the default textures from the CD's as well. Nothing. I re-installed the Silver Wings. Nothing. I re-installed Apt 2.6 and updated the SCASM .exe file with the one from the SCASM website and re-ran the SCASM to create the invisible, lighted runway. Nothing.

I'm wondering if something in the latest "auto-update" for Windows 7 may have done something. That's the only thing I can think of since it's the only change on my machine since I tried to do SCASM runways in the past. I get all kinds of textures with the surface type numbers - both positive and negative - but no invisibility. The texture looks exactly like the picture above.

Has anyone else had this problem? Any ideas?

 

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Hi,

I don't think a windows update will affect how runways in FS show. But the scasm code is old, so maybe fsx does not suppor all attributes correctly. I'll try to do a little test.
 
Thanks, Arno.

I'm using FS2004. The person who started the thread is using FSX.

After further testing it would seem that I am all of a sudden getting the "alpha" of the ".r8" texture when I place the negative switch. For example, when I us "3" as surface I have grass with blotches and can see some of the custom ground. When I use "-3" I get the alpha channel opposite of the grass. Very strange.

Here's the latest code:

========================

;Grand Central Air Terminal, Glendale, CA
;Circa 1957-1959

Header( 0 34.00 35.00 -118.00 -119.00 )
LatRange( 35.00 34.00 )

Area( 5 34.153666757 -118.281166703 24 )
LayerCall( :rwy 24 )
Jump( : )

:rwy

RunwayData( 34.151460041 -118.280839633
Alt 166.116 ;in meters
Heading 319.15
Length 3650
Width 100
Lights 1
Surface -1
ThrLightsN 1
ThrLightsF 1
)
Return
EndA

========================

This started for me just yesterday. I haven't been able to do anything for FS-design in about 3 weeks or so. SCASM runways just happened to be what I picked up when I started back up and next thing I know there are problems. I am glad I checked the forums before posting a thread since I am not the only one with this issue as of late.

Thanks!
 
SUCCESS!!!!!!!

It would seem that we have miss-labeled our runway section as "RunwayData" instead of "Runway" in our code.

Just change this and the thing should work fine.

Guess I shouldn't try to do this too late at night! :D
 
Hi,

when You set the surfacetype to "-1", wich type of effective surface will render on the simulator?

I mean: i know that the runway is transparent (no texture applied), but it have a surface behaviour (asphalt, concrete, grass, turf, ecc.).

Do You have tested rolling an aircraft on it? It is bumpy/waving or flat/hard behaviour?
 
Top