budsurf

This is a beautifully done scenery however, I had to reformat the trees to dxt1 to elliminate the white outline artifacts. The blue edge lights display dark artifacts when illuminated by user aircraft taxi or landing lights....anyone know of a possible fix? Thanks, bud

Does anyone know how to "fix" the TrafficRadarXML.dll module provided by Arne? It's available from Avsim, called 'trafficradarxml201.zip'. The download also has gauge examples and source code. I'm running Fs9. I've managed to integrate it into Ken Mitchell's A320 panel MFD and it works and looks great 'til the dreaded "TICK18 time rollover" when it locks up. I've found the following info: Up with a fresh newsPosted Image there is a small story: recently i was sitting on the apron after another Arne's TCAS gauge test flight. 1 hour "in-flight" has passed long away and suddenly i've decided to resize main panel. and voila! the TCAS gauge was working again!:Hug:So, i became well assured that this is time rollover as i mentioned previously. And where is the problem?ok, look at this part of Arne's code: void MyGaugeCDrawable::Update(void){ lookup_var(&m_tick18); if(m_radar==NULL) return; if(m_owner==NULL) return; if(m_tick18.var_old.n+TICK_MODULO>m_tick18.var_value.n) return; m_recalced = true; m_radar->QueryAiData((int)m_maxnum_act,m_max_range_nm, m_owner- >GetTimeSepTA(),m_owner->GetTimeSepRA(), m_owner->GetDistanceSepTA (),m_owner->GetDistanceSepRA(), m_owner->GetAltitudeSepTA(),m_owner- >GetAltitudeSepRA() ); m_tick18.var_old = m_tick18.var_value;}] ================================================= This is from XMLCCallbacks.cpp If you look presicely you will see (in line 8) that if m_tick18.var_value.n would oddly become zero again, the essential thing of Update call - m_radar->QueryAiData would never happen because m_tick18.var_old.n+TICK_MODULO - (1 time per second updating) would always be greater than that rollovered MS messAnyway, all you need is to add checking for m_tick18.var_value.n and reset the m_tick18.var_old.njust like this... void MyGaugeCDrawable::Update(void){ lookup_var(&m_tick18); if(m_radar==NULL) return; if(m_owner==NULL) return; //additional checking against rollover if (m_tick18.var_value.n<m_tick18.var_old.n) m_tick18.var_old = m_tick18.var_value; if(m_tick18.var_old.n+TICK_MODULO>m_tick18.var_value.n) return; m_recalced = true; m_radar->QueryAiData((int)m_maxnum_act,m_max_range_nm, m_owner- >GetTimeSepTA(),m_owner->GetTimeSepRA(), m_owner->GetDistanceSepTA (),m_owner->GetDistanceSepRA(), m_owner->GetAltitudeSepTA(),m_owner- >GetAltitudeSepRA() ); m_tick18.var_old = m_tick18.var_value;} ========================== But.. there was the other side of the coin . After panel resizing XML variable P:Absolute time rollovers also. Meaning that your favourite clock gauge will show you pretty nice zeros =============================================== 'dragonflightdesign', on 25 Sept 2010 - 12:47 PM, said: You might want to remove the rollover checks completely. There was an undocumented update with FS2K2 when the original UINT16 time limit of 65535 was changed to a 32-bit integer; the rollover period now is in excess of 7.5 years. ACES forgot to update the SDK. ESP also still states 65535, IIRC.-Dai So this means TICK18 has been an UINT32 since FS2K2? Wow, seems to be new to me. Then again, I don't do gauges more than every once in a while, haha. Posted Image Thanks for the "update" despite the dusty thread. :Party:RegardsEtienne =============================================== I'm hoping someone can shed some light on this. Working with dll and C programing are way beyond my ken. Thanks.

Update: I found a nifty little utility called "cursor hider" at: http://www.softexe.com/cursorhider.html?reffer=CHVery nice, it hides the cursor in one second (adjustible), and the cursor doesn't reappear when you change views. Aloha!

Hi, I'm no expert but here's an idea I have experimented with in Fs9. Bear with me here, the possible application to your situation will become apparent soon. I noticed that in Fs9, the propellor drag was not very realistic - while flying, when you chop the power, the propellor should soon produce a major amount of drag, and the plane will slow until it is flying at a speed where the propellor is again producing thrust. To experiment, I introduced an invisible spoiler into the aircraft .air file and experimented with XML gauge code which activated the spoiler through a series of speed ranges using the sim variables - throttle lever position, and indicated airspeed. Example code: (A:GENERAL ENG1 THROTTLE LEVER POSITION,percent) 90 < (A:GENERAL ENG1 THROTTLE LEVER POSITION,percent) 76 > (A:AIRSPEED INDICATED,knots) 125 > && && if{ 16384 (>K:SPOILERS_SET) } By tuning a series of such speed ranges I have made serviceable prop-drag gauges for several planes like the Beaver, Dash8 and E120. Yes I know, very crude, but in the sim this works amazingly well. So, in your situation, you could again introduce an invisible spoiler - but this time have it activated according to aircraft weight, where with a full load there would be a slight increase in drag. As the load decreased, the drag would decrease. Anyhow, the fun is in the experimenting after all.

2 options: 1) Remove VC from model - search "hex editor" in forums 2) Use this xml gauge: <Gauge Name="VCViewSkip" Version="1.0">- <Keys> <On Event="VIEW_MODE">1 (>G:Var1)</On> <On Event="VIEW_MODE_REV">0 (>G:Var1)</On> </Keys>- <Element>- <Select> <Value>(P:ACTIVE VIEW MODE,enum) 2 == if{ (G:Var1) if{ (>K:VIEW_MODE) } els{ (>K:VIEW_MODE_REV) } }</Value> </Select> </Element> </Gauge>

Hi All, continuing my quest to improve the realism while flying at night, (See "Lighted Panel Notes" - Notes on how to add a lighted overlay to an existing panel window), one thing that always bugged me - you toggle one of the view windows at night and the realism is instantly killed because of the bright white cursor on the screen. Eventually it times out and goes away but the damage has been done. It's difficult to remember to move it to the edge of the screen prior to switching views. The fix? You can access your mouse cursor through control panel and select a less intrusive cursor, or better yet, use the nifty freeware utility, IconArt - from: http://www.conware.org/ and make your own cursor.I'm using one which is a medium grey color with the inside of the head of the arrow transparent. IconArt will make/edit Icons AND cursors. Then I used the freeware utility Resourcehacker to extract the other cursors, the hand, plus and minus, and the closed hand, which live in the Fs9.exe file (be sure to first backup in a safe place). I made these cursors a medium grey also and reinserted them back into Fs9.exe with Resourcehacker. Depending on the background color of your favorite panels, one could even have several Fs9.exe files stored somewhere with different colored cursors! Incidentally, resourcehacker is also great for extracting bitmaps from .gau files for editing. Have fun! Aloha from Hawaii!

Hi again, here's some more pics of my finished a320 panel based on the original by Ken "Mitch" Mitchell - thanks Mitch!

Hi all, I thought I'd share some of my notes with other beginners as jazzing up your panels is loads of fun.Notes on how to add a lighted overlay to an existing panel window. Project: To add a nite-lit overlay bmp to the original pedestal window bmp in panel.cfg: Window04=Pedestal ( I.D. = 10 ) <<< The original WIndow04 >>>1) Added new window in panel.cfg: Window07=Throttle ( I.D. = 110 ) And added panel I.D. (110) to FWD Views List2) Made new toggle gauge: NightViews!Throttle: Note: "NightViews" is an arbitrary panel / sub-folder, allows easier access to custom gauges.----------------------------------------------------------------<Gauge Name="Throttle" Version="1.0"> <Image Name="Icon_Throttle.bmp" Luminous="1" ImageSizes="19,19"/> <Mouse> <Help ID="HELPID_GAUGE_TOGGLE_THROTTLE_WINDOW"/> <Cursor Type="Hand"/> <Click>10 (>K:PANEL_ID_TOGGLE) 110 (>K:PANEL_ID_TOGGLE)</Click> </Mouse></Gauge>---------------------------------------------------------------This gauge toggles between Window04 (ID 10) and Window07 (ID 110) and uses original icon bmp.----------------------------------------------------------------3) Put Window07 in panel.cfg with same pedestal gauges as Window04:[Window07]zorder=6 //Note: Original window04 was zorder= 4, this one goes on top.file=Black_Throttle.bmp //<<<<< THIS IS A TRANSPARENT (black 0,0,0) BMP same size as other one >>>>//size_mm=848window_size_ratio=1.000 position=0visible=0ident=110window_size= 0.420, 0.650window_pos= 0.580, 0.460 gauge00=...................etc,etc, Note: some, not all, gauges need to be in both windows.--------------------------------------------------------------4) Made invisible, automatic panel-lighting gauge and put it with original Window04 gauge list: gauge00=NightViews!Pedestal_Nite, 0,0 -------------------------------------------------------------<Gauge Name="Pedestal_Nite" Version="1.0"> <Container/> <Update Frequency="6"/> <Element> <Select> <Value> (A:LIGHT PANEL,bool) </Value> <Case Value="1"> <Image Name="Pedestal_Nite.bmp" Bright="Yes" ImageSizes="848,989"/> </Case> </Select> </Element></Gauge>---------------------------------------------------------------Note: This gauge automatically toggles the night panel pedestal bmp which has the Bright ="Yes" attribute, whenever the Panel Light is turned on, either with a switch, or with key press (Shift+L).--------------------------------------------------------------Note: This same gauge can be added to Fixed Views: Example:[Fixed Window34]file=ll.bmpsize_mm=1024,640window_size= 1.000, 1.000window_pos= 0.000, 0.000window_size_ratio=1.00 position=0visible=0nomenu=1render_3d_window=1ident=34gauge00=NightViews!Left, 0,0 Note: "Left" is the night version of the original left-view bmp. The gauge is: ------------------------------------------------------------<Gauge Name="Left" Version="1.0"> <Container/> <Update Frequency="6"/> <Element> <Select> <Value> (A:LIGHT PANEL,bool) </Value> <Case Value="1"> <Image Name="Nite_l.bmp" Bright="Yes" ImageSizes="1024,640"/> </Case> </Select> </Element></Gauge>------------------------------------------------------------Now you can paint in lighted, though dummy gauges in the part of the panel seen in the forward-right view. I also make darker overlay bmp's of all the Fixed views because the ambient light is too high in Fs9. Now night-flying is very realistic. Have fun!

Hi all, one of my favorite planes is the Project Airbus A319. However, I don't really care for the jetwash effect which is part of the model. You can disable the effect by toggling the water rudder key but I grew tired of having to do it. In Fs9, the water rudders always default to the up position when a flight is started so this simple gauge toggles the water rudders down as soon as engine 1 starts, thus disabling the jetwash effect. I tested this in a Beaver panel which had a water rudder handle to make sure it didn't continually fire, but if someone can suggest a better way to code it, please do so, I'm just a beginner at this xml stuff. Thanks! <Gauge Name="WaterRudder"> <Comment> Toggles water rudder on when engine1 on - bud </Comment> <Update Frequency="7"/> <Element> <Select> <Value> (A:GENERAL ENG1 RPM,number) 1 > (A:WATER LEFT RUDDER EXTENDED,percent) 1 < && if{ (>K:TOGGLE_WATER_RUDDER) } } </Value> </Select> </Element></Gauge>

I managed to decompile a bgl, and used Library Creator to compile the extracted models into a new library which worked fine with RWY12....the objects look great in the sim except there are no lights. I'm pretty sure I have the correct textures in the Static Objects Library and the lights look good in the Lbrary Object Viewer, what's the trick to make the lights work? Thanks...

Hi all, I have several freeware Fs9 airports which have really nice approach lighting structures. I would like to be able to add similar objects to other airports. Does anyone have a group of files making this possible with any of the object placer programs? I've looked into trying to make this myself, but it's beyond my limited understanding. Thanks for any help.

Hi esg,Sure do, but Avsim has a 200kb limit on posted pics - do you know if the pm feature can handle them?

Bad news is, all my gauges are spread all over and it would be a major pain to assemble it all for upload. But, anyone interested, I'll send along the 2 bmp's and even include my panel.cfg - so you'll have all the gauge locations and sizes - just plug in any similar gauges. I modified a lot of gauges, but there are plenty serviceable ones available - check out the other freeware a380 panels.If you've never built up your own panel, it's half the fun of Fs9, I don't even use a panel utility - I do it by hand. Also my panel.cfg is set up for my night panel gauge - I'll send it too. Aloha from Hawaii - Bud

In the night panel I added the above and did some touchup work...

Update: I stuck a gyro repeater into the centerpost top and added a dummy pic into the lower left.

Thanks ESG, good to know, guess I'll just stick a gyro repeater gauge there...laters

Hi, glad you like it. I've seen the site with the 360 degree views of the cockpit, but the numbers on the top round gauge sure don't look like a compass to me. If you've got closeups I'd appreciate seeing them. Laters

Hi all, I'm cobbling together a A380 panel at 1229 x 768 for displaying at 1680 x 1050.Pictures attached - does anyone know what the round gauge at the top of the center post is? It doesn't appear to be either a compass or clock. If I can find out I'll try and make a gauge for it.Anyone like a copy of the panel bmp and/or the nite panel bmp, PM me... Aloha from Hawaii!

Yes! Yes! Me too! Me too!Regards, bud

Hi all, I added this code to Rob Barendregt's Vspeed gauge: </STRONG><Element> <Select> <Value></P> <P> (A:G FORCE, gforce) abs 1.1 > if{ 2 } els{ 0 } (>L:VSPEED_Sound_Turbulence,enum) </Value> </Select></Element></P> <P><Element> <Select> <Value></P> <P> (A:G FORCE, gforce) abs 0.97 < if{ 2 } els{ 0 } (>L:VSPEED_Sound_Turbulence2,enum) </Value> </Select></Element><STRONG> I use two slightly different collections of rattling noises for the sounds. I made the positive g's a little less sensitive to allow for forces during turns. Works nicely, now you can look back at the Project Airbus A319 wing flexing during turbulence and hear the sounds too. Whattcha think? Did I do this correctly?Ya gotta love this xml stuff! Aloha, bud

As an update, I'm using Roman's code (post #4) as a stand-alone for heading-hold and also inserted the code into an AUTOPILOT NAV1 LOCK gauge which also works flawlessly. Thanks again guys - this is really an improvement! Bud

Thanks for testing Jan, I couldn't see how your code could produce 'constant firing' but I'm not very knowledgeable. Just curious, is there a utility which will show if a script is in the 'constant firing' mode?

Thanks very much Roman! Tried your code and it works great.

Thanks a bunch Jan! I'm now running:<Gauge Name="Autopilot Hdg AutoCoord" Version="1.0"><Update>(A:Autopilot heading lock, bool) ! if{ (>K:AUTOCOORD_OFF) } els{ (>K:AUTOCOORD_ON) } </Update></Gauge>//-----------------------------//Works perfectly! Wow, this simple addition really improves the realism of the autopilot heading hold. You gotta love this xml stuff!

Hi All, I tried cobbling together a gauge which would temporarily switch to auto-coordination when the autopilot heading hold is on. This actually works:<Gauge Name="Autopilot Hdg AutoCoord" Version="1.0"> <Element> <Select> <Value>(A:Autopilot heading lock, bool) 0 == ; if{ (>K:AUTOCOORD_OFF) } </Value> </Select> </Element> <Element> <Select> <Value>(A:Autopilot heading lock, bool) 1 == ; if{ (>K:AUTOCOORD_ON) } </Value> </Select> </Element> </Gauge>//---------------------------------------------------------------------------------- I'm betting though, there's a more efficient way of scripting it. Any ideas welcome. Thanks for your consideration.