fx_beaconh bleed through

[jetblst]

Helping out a freeware group get an aircraft ready for release. They would like to get it out by the end of the month.

How does one stop this effect from bleeding through? We like it because it is the closest effect for this aircraft for the beacon. I have tried renumbering the beacon lights. Which works well. IE they are lights 3 and 4. Cockpit lighting and the rest are higher in number so this is the workaround for now.

However all one has to do is turn the beacon switch off and on again and then our cockpit flashes red yadda ya. I have searched to no avail.

Any help?

 

[Nater]

Is this in the VC or is it in the external model...If it is the external model. I do not believe there is a work-around...

 

[jetblst]

Thanks for responding. It is in the VC.

 

[jetblst]

Sorry about that. This is for FSX working on a freeware airliner.

 

[n4gix]

Try editing the default Cameras.CFG file (in the same folder as fsx.cfg file), and add the missing entry for ClipMode...

[CameraDefinition.002]
Title = Virtual Cockpit
Guid = {C95EAB58-9E4A-4E2A-A34C-D8D9D948F078}
Description = This is the description of the virtual cockpit view.
Origin = Virtual Cockpit
ClipMode=Minimum
MomentumEffect = Yes
SnapPbhAdjust = Swivel
SnapPbhReturn = False
PanPbhAdjust = Swivel
PanPbhReturn = False
Track = None
ShowAxis = YES
AllowZoom = TRUE
InitialZoom = 0.7
SmoothZoomTime = 2.0
ZoomPanScalar = 1.0
ShowWeather = Yes
XyzAdjust = TRUE
ShowLensFlare=FALSE
Category = Cockpit
PitchPanRate=30
HeadingPanRate=75
PanAcceleratorTime=0
HotKeySelect=1

 

[Tako_Kichi]

There is a way of doing this by editing the effects file so that it does not show in the VC. Just which parameters need editing I cannot say but A2A managed to get beacons that don't bleed into the VC which they released as part of their 3D Lights package.

 

[n4gix]

That would be the [Properties] section of the .fx file. Works fine in FS9, not used in FSX.

[Properties]
Cockpit=0/1
VirtualCockpit=0/1
Spot=0/1
Tower=0/1
Map=0/1

The [Property] section defines the view modes in which the effect will be displayed.

The FX tool sets all these values to 1. Changing them to zero will have no effect, as these settings are unimplemented.

 

[jetblst]

Nator, Bill, Larry,

Thanks so much but no soap. Still have the bleed through.

Bill what does that ClipMode=Minimum do?

I downloaded your pdf on backlighting last night and I am horribly ignorant at the moment on all things lighting, in cockpits. BUT learning fast. The bleed through only seems to be that beacon effect. The fx_padbeacon works great! BUT it is not what the programmers had in mind. Also I don't recall any airliners having that sort of multi strobe beacon. I drive past KMSP every night and keep looking.

Technically, beaconh is an older style beacon as you guys are well aware Im sure. Most airliners I have seen are a (single strobe red beacon). I wish I had the ability to figure out the timing etc of the fx_padbeacon. Can it be modified to be a single flash? That might fly with the developer.

Sorry to be so picky. The sad news on this is the gentleman who's model this is, passed away last week. They have me as a beta tester. I really want this to be as correct as possible as this is his last work.

I am a RW ATP/CFII so my expertise is in how things ought to be but not how to get there. (yet)

THANKS again fellas! I appreciate looking in to it for me (us). I'll check back for updates. Again. Thank you.

 

[jetblst]

I think I have it fixed!

After a lot of trial and error, I noticed they had 4 VC lights defined.

I also noticed that it wasnt really beacon bleed through like I thought.

The switches and gauges were pulsating. Not an entire bleed through.

So I got to thinking it was a light too far? Again I am a complete newb but
it was my wild guess.

My fix was to remove one VC light. Then rearrange the lights and change the effects from all vc_lightwhi to a mix of vc_light, h and whi

No pulsing switches.

I also noticed that on the lat positions I cannot get closer to the centerline than 1.5 plus or minus.

Anyway it is a fairly decent vc night cockpit. May or may not get approval. But at least we kept one fx_beaconh. (Tail). I could not get things to work with a belly beaconh. Had to stick with the padbeaconh on the belly.

ANY suggestions would be wonderful!

 

[n4gix]

Ah yes, the classic "one bridge too far," or in this case "one light too far..."

I've run into that myself in the distant past. In any event, I quit using "vc lights" years ago, and instead discovered new ways to achieve my end goals.

 

[jetblst]

AH! Is that in your tutorial? My next project is read that through and through.

 

[n4gix]

AH! Is that in your tutorial? My next project is read that through and through.

Most of my tutorial covers backlighting for 2d and 3d gauges on the panel.

The cockpit panel "flood" lights aren't covered, but are an easy adaptation of the ramp lights technique outlined and illustrated in the thread here in the "Showroom" about "33M0 - Leaming Field."

 

[jetblst]

Thanks again for the help guys. The designer loves the job I did on the vc lighting. So that is good.

Bill while I have your attention I am hoping to get a discount on searching here. Trying to save a second or two.

Read your backlighting. I cannot wait to get started.

I did not see in the tutorial anywhere if this would work for an existing panel.

I have a freeware Falcon 10. I really like it as it is the RW plane I fly and they got the air file virtually DEAD ON. So, can I apply the tut to that panel?
I need to rearrange some things on the panel then it will be in great shape. I'd like to tweak this plane I am helping out on too if possible. Can you point me to more of your info? Thanks.

Also does your methodology ever have the dreaded pulse effect I was talking about. Again please forgive my newbness. THANKS!!

 

[jetblst]

Ah one last question Bill.

Recommended software for panels..

FS Panel Studio?

Adobe Photo Shop?

Gmax? Or FSPS? <-- I think that is what it is called.

Finally (probably dumb question but here goes) would I do ok for a while on Paint.Net or other freeware paint shop? Maybe until I get my skill level up?

Again thanks!

 

[jetblst]

Most of my tutorial covers backlighting for 2d and 3d gauges on the panel.

The cockpit panel "flood" lights aren't covered, but are an easy adaptation of the ramp lights technique outlined and illustrated in the thread here in the "Showroom" about "33M0 - Leaming Field."

Wow cool effects. But sadly that is like giving a Caveman the controlls of a 747.

I am still trying to find the master switch, and you send me on the Gopher 5 Arrival to MSP during push.

Ill try that one later. Thanks so much though for the vote of confidence

 

[n4gix]

I'll try to answer your multiple-post questions in one shot...

1. To make use of the techniques described/illustrated in the tutorial you must have the source files. This is non-negotiable as all of the supporting work is done in the modeling program.

2. GMax or Max is best for FS aircraft modeling as they use the SDK tools as designed without requiring extensive and confusing "work-arounds," extra support files, or third-party programs such as "FSDS Tweak" to achieve the desired end results.

3. Photoshop CS4 is my preferred image program, but PaintShop Pro or GIMP are suitable substitutes.

4. Yes, the technique used for ramp lighting does require some degree of pre-knowledge, but it is actually drop-dead simple to implement.

 

[jetblst]

Wow. Thank you so much Bill for all of that. Sorry it was so much.

But after looking at these files for a while now and wondering how the heck, it is like it's finally clicking.

again, thanks!