GrenoZee

I've been experimenting with multiple monitor setups a lot in the past and have no problem running FS9 with multi-mons in full screen mode.You do have to start/switch in windowed mode. You undock the windows you want to have on other monitors, you drag them there and switch back to full screen. Then you just resize and move the windows to your likings and you're good to fly.There are few more details and obstacles, like if you have panels rendered to 3D windows, they have to be on the primary monitor and such, but you figure that out if you come across this ;)But of course, I'm on XP, no idea if W7 brought any "improvements"...

Hi!I've done that before. This in fact is the nose-wheel camera for A380 by Robert Versluys: <Element> <Visible>(A:Circuit general panel on, bool) (L:EXTERNAL CAMERA SWITCH, bool) &&</Visible> <CustomDraw Name="fs9view:view" X="356" Y="340" Zoom="0.50" OffsetUp="-6" OffsetForward="-2" OffsetRight="1"/></Element> This is for FS9 and beware, fs9view:view is a real frame rate killer. If you use this, expect your rates drop down by a lot. Don't know of any other way though and no idea how to do this for FSX.Just modify the offset parameters to get the tail view - but if memory serves me right, you won't see your own aircraft...Hope this helps.

Let me get back on topic here.FS9 is a single thread program. But if investigate a bit in depth, you'll see there are some system threads attached to the process.This is a pure speculation on my side without any good knowledge of Windows internals but I believe this means by restricting FS9 to one core only, you do restrict some threads that could run on the other core as well. When I let FS9 use both cores I do occasionally notice the processor usage jump slightly above 50%. This could be an error in the Task Manager measurements though.But let me clarify that the difference would be so small that you would never notice in in flight.So sure, put all non-FS9 processes to one core and FS9 to the other or both. Btw, if I put FS9 to the first core and all other processes to the second one, my system crashes ;) Got to put FS9 to core 2 and the rest to core 1.Hope this helps.

I've had exactly the same problem and PPWIZARD did the trick for me.It's a standalone pre-processor engine oriented on HTML authoring but XML files are processed just as easily.You put all your macros and reusable code parts to separate files, put references to these in the master files and process.PPWIZARD Link

I did that once and am flying happily since, so it is possible. On the other hand, I've got no payware add-ons...You need to move the FS9 folder to the new location and in Windows registry replace all occurrences of the old path with the new one.Say your sim was in C:\Program Files\FS9 and you moved it to D:\FS9. Search all "C:\Program Files\FS9" strings and replace with "D:\FS9". But if you're not at home in Registry Editor, don't even think of this, it's very easy to screw your system up beyond repair there.And then all the shortcuts in your start menu and on the desktop.

In aircraft like DC-3 you don't control the tail wheel at all. You turn by applying brakes on either the right or left wheel. Best is to use pedals with toe brakes but if you don't have them, hitting the brake and pulling the joystick to a side makes you aircraft turn as well - but it's unbelievably inconvenient. I don't remember whether auto-rudder has to be on or off for this to work.

I have been searching for A380 panel myself and found several, none of which satisfied me enough so I decided to make my own. I'm somewhere around 30% finished but haven't had time to attend to it for more than half a year.If I remember right, I've had crashes with one of the panels (it was the one having almost 50 MB) and the reason was this distribution refers to some gauges that are not included.

My guess is you have turned on the option "Shutdown/restart Windows Shell/Desktop"Un-check this on the Optimization tab and you should have your Windows interface available on FS minimize.

I remember reading some time ago that something very similar can happen while using ATC add-ons like AISmooth.The deal is that these programs in fact slew aircraft when they prepare the landing queue instead of having ATC giving them proper instructions. This can under some circumstances cause the ATC code to loose the aircraft completely resulting in the aircraft proceeding as if no slew occurred... (I'm really not sure anymore about the details, some of this info might be straight incorrect but the general idea is right)Try disabling AISmooth, Radar Contact or whatever ATC add-on you have and see if you still get this behavior.

Chances are I'm about to point something very obvious out but it seems to me you are not aware of the following:There are tools that scan your Gauges folder and notify you of unused ones. One I use is GaugeExplorer and it does the job for me just fine. But to be honest, Gauges are the last of my worries - right now I've got about 300MB of gauges and about 30 GB of scenery and aircraft. I do care about missing gauges but unused ones? Not worth your time ;)Also, if i understand right, that half an hour you're talking about is the FS startup, right? That's WAY too long under most circumstances and one thing that comes up right away: do your AI-only aircraft appear in the aircraft selection menu? If they do, that's what causes such a long startup time. To cure this BBQ Hide AI is your friend ;).Hope this helps a bit...

I can't check right now for the correct syntax but this looks like the panel has render_3D_window (or something like this) set to 1. Try to set it to 0 in the Panel.cfg file.Expect some trouble though since whenever panel designer uses this setting, the panel usually doesn't look or even work well when undocked. A typical example would be a fighter with HUD - undocking and repositioning the panel renders the HUD useless.

I'm sure this has been discussed many times already, so if you need more details, search a bit.In short:Switch to window mode, undock the windows you want on the other monitor, drag them there and switch back to full screen.

Hi!I'm trying to merge the Arne Bartels's Traffic Radar with Ken Mitchell's A320 series MFD and all works very fine - until the traffic on the radar freezes some 20 minutes down the simulation. Even later FS9 tends to crash. I run without problems (mostly) without this gauge.So I wondered, has anyone else experienced similar problems with the traffic radar and might someone have an idea how to fix that?Thanks...

Hi all!I realize much has been said about stutters and I understand well what they are and how to avoid them. But in my own case I'm simply out of ideas and several hours of web searching brought no result.As the topic name suggest, I've got stutters but ONLY when in windowed mode. They come up in very stable period. About every 4 secs the simulation freezes for quarter of a second. Any aircraft, any place on Earth. Full screen mode runs very smooth. If any would have any idea why this could happen, please help me out.I've got laptop, Core2Duo T7200, 2GB RAM. On the secondary video I've got TH2G providing 3 external views covering about 210

I have to disappoint you, this trick actually costs you performance.FS9 runs on one core at a time. You only allow usage of more cores, and the difference between this scenario and staying on one core all the time is that you loose performance on core switching.