RKillins

I have just re-installed FSX and Acceleration fresh to recover from a corrupted install. I had been using DX10 exclusively with what I think may have been the best results possible. Of course, one can always hope to do better. I'm hoping starting from scratch may help. Question: Is there any benefit in applying the tweaks provided by 'Bojote's Tweaking Tool' or those discussed in detail at here? Or will I get the same satisfaction with just concentrating my efforts with Paul J.'s "How To" to optimize my DX setup? I am running FSX in windowed mode spanned across 3 23" monitors using an Nvidia 660ti card. Deciding whether there is any noticeable enhancement running the "preferred" 5760x1080 resolution, or the Nvidia bezel corrected resolution of 6056x1080. Thank you in advance.

Rick, I have a GTX 660Ti and run 3 monitors spanned without the use of TH2GO. Nvidia calls it "surround". I run the three monitors, with DX10, in surround mode with quite commendable quality. I also run a forth monitor off a secondary, basic low power graphic card to display charts (or browse the web during those long flights) on a smaller 19" monitor. To do this though, you have to fly in windowed mode, which when pulled across the real estate of the three monitors, autohide taskbar, is pretty much like flying in full screen mode anyway. The cavaet though is that the 3 monitors have to be the same size and refresh rate to work. It's easiest if all three monitors are the equal. There are also problems experienced with the higher resolution (ie mine is 5760x1080x32) when it comes to pop-up panels and alternate views. FSX isn't prepared for the big resolutions, and if you're lucky, the panels will just be grossly sized. In the worst case scenario, the panel/view will "disappear", leaving you with a spinning constantly busy Windows 7 cursor. The way around that is manually resize and position the panel / view by editing the panel.cfg for the particular aircraft. There is some minor distortion to the view to far left and right extremes of the display, but everything in the centre monitor is fine. This can be lessed with a tweak to your fsx.cfg file.

Hello all, I am cross-posting this post from my original post at Flight1's exclusive customer only support forum. As my issues may not necessarily be a product flaw, I'm not certian how quickly, if at all, they will reply. I'm asking the same questions here in anticipation that there are people that have had similar problems, exclusively with the Flight1 Citation Mustang or other . These are irritating problems that unless I can get them resolved will truely take away the enjoyment of this reportedly fine piece of simulation. I have purchased and installed v1.08 for my FSX (Acceleration), and as strongly recommended by Flight1 installed the FSX Safe Startup for Complex Aircraft. Loaded up flight with this configuration, changed aircraft to the Mustang, and changed airport and weather. Re-saved as default flight, so now each time I start a flight, it's with the Mustang at KORF. Launched FSX with the new customized default flight. The VC view was active, and the engines were running (despite the displays being black ... one would think the plane was in a cold and dark state ... but cranking up the panel display lights reveals fully populated and functioning displays) Immediately encountered these problems. Problem 1: Flickering MFD and with the flashing/spinning Windows 7 cursor bug common with when using higher resolutions over spanned monitors. I'm using 3 23" monitors in a Nvidia surround setup with resolution 5760x1080x32. This is not a new phenomenon for me and experienced with most aircraft in my hanger, but usually only prominent when using panels or other views which with painstaking manual editing of the panel.cfg file I can in most part overcome them. This is the first that I've encountered the problem with a default VC. Only the MFD flickers. I've attached a link to a video taken immediately after starting the flight. Nothing has been touched. The flight opens on the one monitor, and suffers from flickering even before I stretch it across the 3 monitors. Thevideo capturing software doesn't do justice in accurately representing the problem. The cursor flickering bug isn't well depicted, and the MFD flickering is not a rapid. The video isn't even across all three screens. Only on one. The flickering starts immediately when the flight initiates and before I even stretch the window across the 3 monitors. Notice from the video also the displays are dark (except the MFD. I have to use the cockpit panel light knob to brighten them up. This seems odd as well. I'd prefer if they were lit when fired up. Problem 2 : I'm finding several switches not working. Perhaps they aren't supposed to, but they seem pretty important. Switches like the L/R GEN, BATT, Avionics STBY/BATT Test, Fuel Boost, Wing/Stab ice protection, Pitot Static, L/R Engine Start, PAX Safety Seatbelt, do not do anything. I'm hoping to be able to tweak my default flight to a cold and dark setting, but it seems I'm unable to to turn off many of the systems as the switches don't respond. Problem 3 : Throttles don't advance,whether by using the mouse or the Saitek pro throttle controls (All other assigned buttons and axis work on them, just not throttle) The throttles do advance in power, just that the levers don't move. Problem 4 : If I switch off the Avionics Power switch, should the display not go dark? Not the case in my scenario. Problem 5 : I opted to try and get some functionality from the switches by going to their respective 2D panels in the Instrument views. The Left Switch Panel was selected but disappeared immediately. The only way I was able to get it visible in the forefront, was to edit the panel.cfg panel and resize and reposition the panel. Only after that did the panel appear. But nothing functioned off this panel! Any clicks on switches simply selected the panel window, with which I could drag the window around. The panel had no functionality. Link to video: https://docs.google.com/file/d/0B9EE-tbOy4bJZVFVQkU5RDlQazQ/edit?usp=sharing

Thank you Riccardo, great input. Good to know about the frame rate impact, I know now not to have great expectations. Now, hopefully I can get the support to deal with the issues I'm having without having to consider DX10 as being the cause.

Does anyone on this list fly the Flight 1 Citation Mustang with DX10? Is so, have you experienced any issues as far as operation etc? "We don't support DX10" is a common way out of product support. As soon as you say DX10, it's automatically the culprit and no further support is offered.

Thanks to all for your follow-up messages. Adam, thanks for sharing your resources. I also use FltPlan.com for current charts for North America. I am also a subscriver to Navigraph, and my Embraer jets are kept up to date with their current AIRAC data. That is the information I provided in my FMS. I acknowledge your hints for arrival and approach. Rendi ... the simple alternative would be to eliminate the hold out of this procedure (I think that's what I ended up doing out of frustration anyway. I'm sure all my tinkering around would have no doubt took a toll on a controller's patience!). Knowing how to deal with this appraoch though could be a great learning experience. In this case, the hold was indeed providing a course reversal. So, I'm in the hold, how do I get out to proceed to intercept the localizer when I'm inthe holding pattern? In the meantime, I'm going to see what advice wims' links might provide!

Thank you all for your your valubale insights and experience. I was using the Embraer's FMS to determine TOD, and am theoretically familiar with the 1:3 rule many of you have referred to. I think it was in lrge part a mis-understanding of the FMS and autopilot that was creating a much of my problem. I'm still unsure exactly what the FMS controls vs. what the pilot controls on a descent, arrival and approach. I know that the FMS provides altitudes (VNAV), waypoint navigation (LNAV) and speeds based on procedures, but does the autopilot utilize them, or are they for pilot reference for manual flying? Despite the FMS info, previously it would appear the autopilot failed to recognize them. Regardless, I had quite a successful descent last evening in another practice flight. I began my descent based on the calculated TOD, and the descent was smooth and on target for the suggested altitudes at the different waypoints as per the procedure. Without jinxing myself, I think I have a more reliable understanding of the descent. I ran into further misunderstanding when it cam time to to execute my approach. This is a combination of not thoroughly understanding navigational techniques (auto vs. manual) and proper sequencing of aircraft controls. Consider the ILS approach Rwy 35 into KILM (Wilmington, NC) I was on last evening. Uploaded with ImageShack.us And it's depiction in the Embraer's FMS: Uploaded with ImageShack.us Uploaded with ImageShack.us My interpretation, which likely needs correcting, is ... Intersect VOR ILM on descent to waypoint FI35 (which I believe is NDB IL) maintaining 240 knts ... controlled by engaged VNAV, LNAV, AT on autopilot At FI35, commence holding pattern at 1900' (uncertain as to the meaning of the 3.0o and DES). I noticed that the autopilot put me into the hold, and maintained me in the hold. At this point things went downhill. Seems I found myself stuck in the hold. I assume in normal circumstances, ATC will advise when to exit the hold, but without ATC, is there a point in the procedure I would exit? How do I exit the hold? By selecting the LSK6 button ("Exit hold") I assume. By doing that, what is the next move performed by the FMS/autopilot or pilot? Will it take me to the next waypoint in the flightplan, ZUDRU? Or are the three points F!35-ZUDRU-FI35 just points of the holding pattern? So, once I exit the hold, what is the next sequence to get me established? My NAV1 and NAV2 are set to localizer freq. 110.3. My guess is there is a point in this sequence where I switch from FMS to V/L mode? A point where I need to adjust my heading and CRS? And a point where I have to switch from NAV to APP mode? It's the holding procedure which is mixing me up ... many of these questions I can assume an answer with a nice straight in ILS approach. My apoplogies in advance for being long winded, and seeking "hand holding" for what should be very basic tasks. I have sought references to self teach, but found much of the information too generic and struggled with trying to apply it practically. Thanks friends.

I am wondering if anyone knows of any good thorough tutorials or references that will help me understand the different stages of arrivals and landings. Descent planning, speed and altitude control, FMS and autopilot role and use in arrivals etc. I've been quite unsuccessful in landing my Embraer 170 ... most times descenting too late and then compensating with drastic rates of descent and increased speeds. I know it's likely a very broad subject, but even knowing the basics might be a help.

Wow ... quick reply Jim. I was just in the process of editting (trying to retract actually) my OP. Turns out that the time setting changed after I hit Free Flight. I noticed it when I went back to change some other settings. After I reset it to 7:15PM, the depiction was correct.

Disregard

My apologies for failing to reply in the wrong format ... Thank you folks ... appreciate your time. From what I gather, having this in the FMS really has no benefit, other than reference information. One would still be having to semi-automatically control the heading and altitude through departure to the first fix anyway.

My apologies if this isn't the appropriate forum to ask this question. I pondered where the best fit would be, and felt this might net me the best response. I am enjoying FeelThere\Wilco's ERJ170/190 Regional Jet series. I'm using what documentation and tutorials I have to try and master a flawless flight between departure and arrival. I have a question about interpreting FMS flight plan entry and using the autopilot with said information. I can enter a flight plan and undertand the basic logic behind what I see. However, I get a bit confused when I add a departure SID. Attached is a capture of my FMC after I inserted the KISSR1 SID out of Norfolk International (KORF). Uploaded with ImageShack.us I would be very appreciative of anyone that would be ale to explain what I am seeing. Obviously RW05 is the departure runway, 47o I assume refers to the runway heading. But I cannot relate to: "F 0.9NM", "1435^ CLB" , "*ALT03 00+00" "---/0430A" "Fly 047o or as assigned" Is there any enhancement to this inserted SID that I need to manually provide to make it effective? I know I have to remove the ">> DISCONTINUITY <<". Do do so, I have had to delete the "Fly 047o or as assigned" entry at LSK 3L. Not sure if this is right. So, once the SID is inserted, and flight plan is activated, will the autopilot fly it? At what point would I activate it? What needs to be activated ... NAV? VNAV? ALT? (Still rusty on the autopilot). Before i discovered that I can add the SID, I would manually fly the departure, maintaining runway heading and climbing to 4000' (AP > HDG 047 > VNAV > Alt 4000) before adjusting the heading to intercept the NAV to FORTS and climbing to filed altitude. Thank you in advance for your patience.

Thanks Danny, that "appears" to have done the trick. Although "Brakes" still appear iun the bottom left corner, at least I can move now. (Whether it's effectively moving ... full throttle to get the Twin Otter to start creeping)

I read alot about people's un appreciated experiences with "shimmering". My apologies for being ignorant, but how would one describe "shimmering". The reason I ask, is because I have noticed since playing around Nvidia Inspector, that buildings, or distant urban areas, and AI aircraft at airports, especially from a distance, seem to twinkle. It doesn't appear to affect performance ... but it can really be distracting. I am running DX10 preview, 8xSQ (Combined: 2x2 SS +2x MS), 4xSS set in NVI, with in game Anistropic ant-aliasing selected. If the term shimmering is a mystery to me ... so are these settings ... so I admit my incompetance when I say I have no idea how, if at all these settings influence what I see. If what I am experiencing can be fixed, I acknowledge in advance anyone's advice on appropriate resources to check out, or any advice sent my way.

I use the Saitek Pro yoke and and pedals with my FSX install. When I am taxi and use the left and right toe brakes, they function properly. However, when I release them, the "Brakes" message appears in the lower left corner of my display and eventually my aircraft stops. The only way it seems I can release the brakes and resume forward movement again, is to set and release the parking brake. But as soon as I use the toe brakes again, the plane stops. Do I have a bad setting somewhere?

Still struggling with starting this bird. My biggest issue is getting fuel to the engines. Both left and right main pumps are on, the two standby pumps are auto. The two standby pump lamps are illuminated green ... but I am unable to get green lights for the fuel supply to the left and right engines. Condition levers are at 2%, left throttle is at low idle, 2% also. Propeller is 100%. I have lots of fuel. Engine will not start with the starter engaged. Obviously I am missing a critical step.

I understand that I can get external power if I have Acceleration installed. I do, but switching GRD PWR on appears to not do anything. The only options in the control panel under ext are OFF and N/A. Am I missing something? And I can't seem to reverse the Basler. Tail wheel locked, brake off, Power levers in reverse, condition lever full. Instructions say Propeller in reverse, but how? I can only pull it as far back as the red/yellow hatching.

Awesome reply CoolP. Thanks for taking the time to explain and demonstrate with the pics. Very much appreciated. Happy to say I got flying, and with two engines! The trick was using the condition levers independently.

Thanks CoolP for your reply. I'm not all up yet on the jargon ... so excuse my ignorance if I seem to be seeking further explanation of the obvious. I use the Saitek Pro Yoke system with the three levers, black, blue and red from left to right. The controls operate both L & R engines simulatenously, so I wonder if I need to operate the L & R controls independent of each other, one at a time rather than together with the Saitek controls? So, to recap ... Condition lever (red ... right) in cutoff position. Wait for 10% rotation ... which is indicated by torque? (gauge and control panel indicator) Fuel Flow setting (black lever ... left) to idle. Does the condition lever remain in the cutoff position at that point still, or is it advanced?

I am finding it difficult to start both engines of the Basler BT67 (by Fuernkaess, Jahn, Metzger and Naegele). I have followed the documentation, and am able to only ever get one of two engines started. I don't know what I'm doing wrong. I'm not sure if the line highlighted in blue from the documentation is a typo or not, but I have to have the condition on (opposite fuel cutoff) With left engine started, - right hand main pump on, - right hand ignition start - power lever at low idle - press and hold the start button .... just turns over and over .... Engine #2 PSI maxes at 53, and RPM 19. (Note: I understand this release features "tips" when you hover the mouse over areas in the control panel. This does not, and never has, worked for me.)

Hi Shakeystick, Let me chime in here with my experiences using multi-monitor setups, and some of the common problems you are experiencing. - Not a DX10 issue. :-) - I believe that the only multi-monitor scenario allowing a panoramic cockpit view would be to use Nvidia's surround mode with it's cards (or TripleHead2Go). Not sure how you did it without using surround. Understand, that to use surround effectively, you must ensure you have three monitors of equal size, resolution and refresh rate. It will not work without. Even fair to say to avoid problems to use identical monitors. - SLI will not bring you any performance boost in FSX, but I realize in your situation, this is the onloy way you are able to use multi-monitors. (I had a similar setup) - you can run your fourth monitor, but it will be independent of the primary FSX display. I use a second (or 3rd card in your case) dedicated to this monitor as a support reference hosting 2D panels, mapping and charts. However, to do this, you have to run FSX in windowed mode. In full screen mode, the fourth monitor will be blanked out and not useable. - the VC when spanned across the monitors will be grossly exaggerated, but can be easily fixed by adding the setting WideViewAspect=True in the [Display] section, if it's not there already. See this post. Still not perfect, but a big improvement and far more useable. - the spinning, always active, frame busting, Windows icon is a result of accessing 2D panels in surround mode. I don't know the technical details of it all, but from what I understand, the panels weren't intended with such high resolutions in mind. When I first encountered this, it annoyed me huge! Nothing worse than being 45 minutes into a flight and accidently pulling up an instrument panel only to have tyhis happen and be forced to abandon the flight. Try this link, it explains the problem and goes into the solution. It will involve a manual editting of each of your aircraft's panel.cfg files. (I have a small Excel application that has made this task less painful allowing me to perfectly resize and reposition the panels as I see fit. I currently use 1 EVGA GeForce 660ti card to drive Nvidia surround across my 3 23" ACER LCD monitors. This was an upgrade from my previous 2 EVGA GeForce 560ti cards in SLI similar to yours. I use an older GeForce 8500 card to drive my fourth 15" resource monitor. It doesn't have to be anything high end for it's purpose. As mentioned first off, this isn't a DX10 issue. I am running FSX in DX10 mode with Nvidia surround with a resolution of 5760x1080x32 with great satisfacftion. Frame rates are averaging about 20-25FPS.

Thanks Jeff, Turns out a re-install of UTX resolved the issue. For now. This is a recurring issue, that I have yet to isolate the cause. It either happens when I switch between ORBX Oceania and ORBX NA, or when I install new scenery/airports. I do not habitually play with the scenery layout (not to say I've never been in there), so the mis layout at times is a mystery.,

Is anyone able to recommend a decent Fairchild Metroliner with VC for FSX. I've searched the file libraries resulting only in FS2004 models, or modified FS2004 for FSX models with only 2D panels.

Hi Jeff, thank you for the reply. I continue to still have issues with the corrupted terrain. I've re-ordered the scenery library as suggested to reflect UTX required order, but the terrain and overhead views are still corrupt. In an attempt to debug, I have tried disabling "Jim Dhaenen's Scenery Objects", "Edwards_AFB", "Ontario Default Landclass" and "Ontario Custom Farmland Landclass" entries with little change. The problem appears to be within Canada only, however, I've included screenshots of both the US and the UK as I'm not sure if the dark water is normal or part of the corruption. Georgian Bay, Ontario Canada Halifax, Nova Scotia, Canada Boston, Massachusetts, USA United Kingdom Is anyone able to help me figure this frustrating situation out? Thank you in advance.

When I initiate a flight, "Fly Now", the scenery and other loading processes complete fine and I am placed at my destination. However, if I exit to change a setting for instance, and "Fly Now", FSX crashes to a grey screen while loading terrain (crashes at 0%). It appears that any subsequent attempts to fly after the initial configuration has been loaded fails. Has anyone had similar experiences that could share their means of resolution? Or perhaps someone has a theory on what may be happening in this case that may be creating this problem. This is very frustrating when you simply want to change the time or parking location for instance.