Hi Les,Thanks again for trying to help me here. I thought you might have had the solution too. I tried disabling User Control but no difference. Regards, Tom

Thats very disappointing. Disabling UAC has cured the the blank 2D panels and flashing cursor running under windows 7.If someone with more technical knowledge can explain why this should be, we might have more chance of a solution without compromising security.My diagnosis is that FSX is trying to repeatedly (hence the flashing cursor) load the 2D panel (only seen in the forward view) but that a security setting is blocking this operation. This process continues even when the view is changed to Virtual cockpit. This may have something to do with accessing the Maxtor TH2G black box device.By the way, X-plane is a different program to FSX and I see no reason to suppose that it should behave in the same way. Since Aces Studio is not supporting FSX any more this may be simulator of choice now.Regards Les

May I recommend....http://www.widescreengamingforum.com/forum/This is the WideScreen Gaming Forum, and is THE support forum for users of the TH2G. Scroll down to the "Surround Gaming" section (it is the section for the TH2G, and there are 3 sub-forums in it), and post your problem there. Tons of FS TH2G users there who can probably help you.I don't currently use the TH2G Digital Edition, nor widescreen monitors, so I'd be guessing for you right now. But there are plenty of users there who do, and lots of help offered for TH2G users.Rick

As an afterthought for the original poster's problem with switching from VC to 2D cockpits causing problems, I just remembered something else.There was a known "bug" in FSX at one time that caused this problem if the "Show Cockpit Tool Tips" option was enabled in FSX. I honestly don't know right now if this is still a problem in FSX or not. But it is something you could try.Uncheck the "Show Cockpit Tool Tips" option in FSX, and see if it fixes the problem. If not, no harm no foul. You can always turn it back on again.Rick

As an afterthought for the original poster's problem with switching from VC to 2D cockpits causing problems, I just remembered something else.There was a known "bug" in FSX at one time that caused this problem if the "Show Cockpit Tool Tips" option was enabled in FSX. I honestly don't know right now if this is still a problem in FSX or not. But it is something you could try.Uncheck the "Show Cockpit Tool Tips" option in FSX, and see if it fixes the problem. If not, no harm no foul. You can always turn it back on again.Rick

Rick,I held my breath and tried your suggestion. Unfortunately, it was disabled anyway. Thanks again and please keep trying! :( Regards, Tom

TomOne more thing to try. Visit Flight1 WebsiteThere is some good advice there for Vista users. In addition to disabling UAC, they recommend and describe in detail how to take full control of files in your 'Program files' folder. Yes, even though you paid for them, installed them, and you are logged on as administrator you are probably not the present owner of FSX files or your other programs for that matter.This has certainly finally solved my display problems with cockpit chatter running under Vista HB.Les

TomOne more thing to try. Visit Flight1 WebsiteThere is some good advice there for Vista users. In addition to disabling UAC, they recommend and describe in detail how to take full control of files in your 'Program files' folder. Yes, even though you paid for them, installed them, and you are logged on as administrator you are probably not the present owner of FSX files or your other programs for that matter.This has certainly finally solved my display problems with cockpit chatter running under Vista HB.Les

Hi Les,Just to bring you up to date, I have also been monitoring replies at http://widescreengamingforum.com/forum/viewtopic.php?t=16678 regarding my problem. They have come back with some interesting points but unfortunately no solutions. I just can't understand how this issue hasn't been resolved since others have apparantly experienced it also. The one suggestion of not using TH2G after paying $300 for it is definitely not my favorite. Hopefully, someone out there will be the hero with the solution. Regards, Tom

Hi Les,Just to bring you up to date, I have also been monitoring replies at http://widescreengamingforum.com/forum/viewtopic.php?t=16678 regarding my problem. They have come back with some interesting points but unfortunately no solutions. I just can't understand how this issue hasn't been resolved since others have apparantly experienced it also. The one suggestion of not using TH2G after paying $300 for it is definitely not my favorite. Hopefully, someone out there will be the hero with the solution. Regards, Tom

Hi Tom,I have managed to reproduce your symptoms running under Vista HB by utilising a fourth monitor that I have connected to the second video outlet of the Radeon 4800 series card. Using 'windows display settings' I have extended the desktop onto this extra monitor. Unfortunately because this is a smaller 15in monitor it is not that neat but it suffices.Experimenting using a screen resolution in FSX of 3840x1024x32 gives the following results:-1) It is not possible to extend the virtual cockpit or the outside view in the 2D cockpit over the extended desktop.2) It is possible to stretch the 2D panel (gauges etc) to occupy all of screen 1 and about 5cm of screen 2.3) Stretching the 2D panel greater than this width gives a black panel and the flashing cursor.Perhaps you could do a similar experiment to see if there is a maximum width of window on your setup. I am assuming here that you can display a 2D panel in a window occupying just one of your screens.Les

Hi Tom,I have managed to reproduce your symptoms running under Vista HB by utilising a fourth monitor that I have connected to the second video outlet of the Radeon 4800 series card. Using 'windows display settings' I have extended the desktop onto this extra monitor. Unfortunately because this is a smaller 15in monitor it is not that neat but it suffices.Experimenting using a screen resolution in FSX of 3840x1024x32 gives the following results:-1) It is not possible to extend the virtual cockpit or the outside view in the 2D cockpit over the extended desktop.2) It is possible to stretch the 2D panel (gauges etc) to occupy all of screen 1 and about 5cm of screen 2.3) Stretching the 2D panel greater than this width gives a black panel and the flashing cursor.Perhaps you could do a similar experiment to see if there is a maximum width of window on your setup. I am assuming here that you can display a 2D panel in a window occupying just one of your screens.Les

Hi Les,Forgive me, but I know very little about this set up of mine and how to adjust the display. I have a very similar Display Settings screen to yours (I didn't know how to attach it as you did :( ), and I know little about adjusting it. It would be great if I could keep the stretched display across the three monitors for the 3D virtual display, and if I pick the 2D window, have it open on just one screen with the subpanels such as throttle quadrant, radio stack, etc. open on the other 2 screens in some arrangement. The problem is, if I try and open a subpanel now even when in the 3d display, it starts up the cursor problem. I don't even have to open the "black rectangle" 2D window. It happens just selecting an aircraft panel regardless of what window I have open. That's why I am basically stuck using FSX till I solve this. If it were just the 2D window problem I originally thought, I would just use the 3D and try and avoid the 2D. But I can't open any smaller subpanels either without setting off the cursor. That's the main problem at this time. I have the Level D 767 and when in 3D mode, I get a beautiful cockpit view across the three screens, but I can't select any subpanels without setting off the cursor, and I can't even open the overhead panel at all. I do have a second video port on my ATI card, but a surely can't afford a fourth monitor and don't have room for it anyway. Do you know if I can set my display up someway that I would have the 3D view open across the 3 screens and then when I open a subpanel or 2D window have them open on the single monitors? Thanks a million. Tom

Hi Les,Forgive me, but I know very little about this set up of mine and how to adjust the display. I have a very similar Display Settings screen to yours (I didn't know how to attach it as you did :( ), and I know little about adjusting it. It would be great if I could keep the stretched display across the three monitors for the 3D virtual display, and if I pick the 2D window, have it open on just one screen with the subpanels such as throttle quadrant, radio stack, etc. open on the other 2 screens in some arrangement. The problem is, if I try and open a subpanel now even when in the 3d display, it starts up the cursor problem. I don't even have to open the "black rectangle" 2D window. It happens just selecting an aircraft panel regardless of what window I have open. That's why I am basically stuck using FSX till I solve this. If it were just the 2D window problem I originally thought, I would just use the 3D and try and avoid the 2D. But I can't open any smaller subpanels either without setting off the cursor. That's the main problem at this time. I have the Level D 767 and when in 3D mode, I get a beautiful cockpit view across the three screens, but I can't select any subpanels without setting off the cursor, and I can't even open the overhead panel at all. I do have a second video port on my ATI card, but a surely can't afford a fourth monitor and don't have room for it anyway. Do you know if I can set my display up someway that I would have the 3D view open across the 3 screens and then when I open a subpanel or 2D window have them open on the single monitors? Thanks a million. Tom

Hi Tom I appear to have confused rather than helped you.Try this.1. Start FSX2. Hit 'Fly Now' button.3. If the ubiquitous 'Minimise';'Maximize/ Restore'; 'Close' buttons are not dispalyed in the top right hand corner of your display then press 'Alt Enter' to switch from Full Screen to Windowed mode.4. Ensure that you have a window border down the rhs of the display. If not then press the 'Maximize/ Restore' button.5. Move the mouse over the rhs border until it changes to a double headed arrow and then drag the border to the left until the display occupies just the left and centre screens.6. Bring someone into the room you want to impress and change to 2D view. :( 7. Assuming your guest is suitably amazed, try undocking some of your other 2d panels and moving them onto the right hand display.8. If your heart can take the strain, experiment by dragging the border onto the right hand screen. I reckon you should be able to get half way across before your symptoms return.I think that quite enough of me sticking my neck out.Les

Hi TomI dont know if you already solve your problem but this can help.Start FSX as says Les up to the point 5Resize roughly your windows in the center monitor.If it's not the case turn the display mode to 2DShow the 2D panelRight-click into the panel and select the menu line saying something like "detach the window" (Sorry, I'm french and I use a french FSX. I dont know what are the english messages). If you succeed, you must see a frame around the panel. At that point, the panel can be moved and resized as you want. Leave it where it is.Maximize your main Fsx window. There is 2 way for that:1) drag manualy the borders2) or click the 'maximize" button on the top-right corner. If you have properly preset Matrox PowerDesk to maximize 'In current Windows display', FSX will cover all the three screenDrag and resize your panel where you want. If you have another (fourth) monitor like I do, you can place it on this other screen.The crazy cursor you have seen typically append when Fsx 'loses' a window. In your case, it loses the 2Dpanel.I know there is a trick to recover such lost window without killing FSX, but I can't remember where I've read it. Sorry.

I'm sorry I can't offer any fix, but I can offer some information that I don't think has been mentioned in this thread so far. When I researched the TH2G before I bought mine this fall, there did seem to be several mentions of problems with Radeon graphics cards as I was reading through several forums and reviews. I came away with the general feeling that the TH2G was not nearly as compatible with Radeon cards as it was with Nvidia cards. I did notice above that you are using a Radeon. I use Nvidia here, and am currently playing FSX with Windows XP Home SP3 on a GeForce 9800. It works very well across the 3 LCD displays, and I was even able to crank up all most all the graphics settings to their highest while using the 3840x1024x32 resolution. Perhaps some Radeon drivers might work better than others? Sorry I can't be more help. Good luck!Zoandar

To the op and anyone else reading this, I posted information about this just earlier today. I've made a set of updated panel.cfg files for all the stock aircraft that should fix the op's problems (if he hasn't gotten them fixed yet.)More information: http://forums1.avsim.net/index.php?showtopic=269852Good luck.-George

Try running 4080x768 like me (for three wide screens), running on XP still. But there

Hello I didn't read the whole thread, but the gist of it is you can't get your 2d panels up?I have the same setup at 5040 x 1050, to get the panels to work, you have to change the size that they load up.Try this with a default craft. go to panels and save a copy of the panel.cfg for backupnext edit it and change every 2d panel by adding the following or changing what is there to the following:window_size= 0.333, 1.000The problem is that FSX sees the window as a huge size and tries to load the panel graphic accordingly, that way the program will load up the panel at normal size and you are good to go.I have personally done this on several default craft and the wilco erj (payware), there are still some craft I can't get it to work 100% (level D 767 and the Flight 1 Mustang)This is what the end result should look like, this is a merged craft I made using the default 737 cockpit. This is in full screen mode, windowed mode does not help.Here is my panel cfg:[VIEWS]VIEW_FORWARD_WINDOWS=MAIN_PANEL,GPS_PANEL,THROTTLE_PANEL,OVERHEAD_PANELVIEW_FORWARD_DIR=-1.000, 0.000, 0.000//--------------------------------------------------------[Window00]file_1024=../panel/737-800_panel_background.bmp file_1024_night=../panel/737-800_panel_background_night.bmp size_mm=1024position=7visible=1ident=MAIN_PANELwindow_size=0.333, 1.000window_size_ratio=0.333gauge00=B737_800!pfd_screen, 189,548,218,219gauge01=B737_800!pfd, 210,567,179,179gauge02=ISG1!HW_B737_ND, 406,549,219,217,B737_800gauge03=B737_800!eicas_screen, 740,548,218,219gauge04=B737_800!eicas, 760,565,179,179gauge05=B737_800!compass, 839,39,91,62gauge06=B737_800!autopilot, 561,330,463,90gauge07=B737_800!knob_1, 329,501,31,35gauge08=B737_800!knob_2, 390,501,31,35gauge09=B737_800!knob_3, 830,480,31,35gauge10=B737_800!clock, 77,570,105,105gauge11=B737_800!attitude_backup, 630,444,104,105gauge12=B737_800!adf_vor_backup, 630,662,104,105gauge13=B737_800!alti_and_asi_backup, 631,555,103,103gauge14=B737_800!gear_lever, 959, 524 ,65,241gauge15=B737_800!annunciator_below_glideslope, 214,517,52,27gauge16=B737_800!annunciator_le_flaps, 854,516,100,28gauge17=B737_800!annunciator_speed_brake_armed, 516,516,51,28gauge18=B737_800!annunciator_auto_brake_disarm, 823,441,47,27gauge19=B737_800!annunciator_anti_skid_inop, 812,517,37,27gauge20=B737_800!efis_control_panel, 416,344,143,76gauge21=B737_800!flap_indicator, 892,452,59,59gauge22=B737_800!annunciator_panel_1, 267,361,132,40gauge23=B737_800!annunciator_panel_gear, 958,454,66,71gauge24=B737_800!Knob_N1_Set, 755,454,43,46gauge25=SimIcons1024!ECU Icon, 433,448,19,19gauge26=SimIcons1024!Overhead Icon, 455,448,19,19gauge27=SimIcons1024!Kneeboard Icon, 477,448,19,19gauge28=SimIcons1024!ATC Icon, 499,448,19,19gauge29=SimIcons1024!Map Icon, 521,448,19,19gauge30=SimIcons1024!GPS Icon, 543,448,19,19gauge31=SimIcons1024!Radio Icon, 565,448,19,19gauge32=SimIcons1024!Other Controls Icon, 587,448,19,19gauge33=n_number_plaque!n_number_plaque, 95,731,67,19gauge34=ISG1_TCAS!Logic, 1,1,1,1gauge35=ISG1!FMS_OPEN, 566,471,25,25gauge36=isg1!MCU_OPEN, 566,497,25,25gauge37=isg1!LNAV, 592,471,25,25gauge38=ISG1!VNAV, 592,497,25,25gauge39=ISG1!EFIS_CTRL_OPEN, 566,524,25,25//--------------------------------------------------------[Window01]Background_color=16,16,16 size_mm=159,441position=8visible=0ident=RADIO_STACK_PANELgauge00=737-400!Comm 1, 0,0,159,68gauge01=737-400!Comm 2, 0,68,159,68gauge02=737-400!Nav 1, 0,135,159,68gauge03=737-400!Nav 2, 0,203,159,68gauge04=737-400!Transponder, 0,271,159,68gauge05=737-400!ADF, 0,340,159,68gauge06=737-400!Audio, 0,409,159,32//--------------------------------------------------------[Window02]Background_color=0,0,0 size_mm=456,378position=8visible=0ident=GPS_PANELwindow_size=0.333, 1.000window_size_ratio=0.333window_pos= 0.000, 0.000gauge00=fs9gps!gps_500, 0,0//--------------------------------------------------------[Window03]Background_color=0,0,0 size_mm=265,394position=0visible=0ident=THROTTLE_PANELgauge00=B737_800!ECU, 0,0//--------------------------------------------------------[Window04]Background_color=0,0,0 size_mm=197,271window_size_ratio=1.000 visible=0ident=4004window_pos = 0.7402, 0.4122window_size= 0.250, 0.500gauge00=isg1!SMITHS_FMS, 0,0,197,271//--------------------------------------------------------[Window05]Background_color=0,0,0 size_mm=581,529position=2visible=0ident=OVERHEAD_PANELwindow_size= 0.333, 1.000gauge00=B737_800!overhead_popup, 0,0//--------------------------------------------------------[Window06]Background_color=0,0,0 size_mm=194,154position=1visible=0ident=MISC_POPUP_1gauge00=B737_800!trim_popup, 0,0//--------------------------------------------------------[Window07]Background_color=0,0,0 size_mm=315,310window_size_ratio=1.000 visible=0ident=4013window_pos= 0.7332,0.0922window_size=0.2500, 0.2500gauge00=ISG1!HW_B737_EFIS_CNTR, 0,0,315,310//--------------------------------------------------------[Window08]Background_color=0,0,0 size_mm=312,214position=4window_pos= 0.1541,0.3133window_size=0.1888,0.2044visible=0ident=4001gauge00=isg1!MCU, 0,0,312,214