defaid

Hi Alex. This may seem like a stupid question but are the two pictures from the same set of folders? The texture SBAI_MI-8MT_T.BMP does not seem to be in the correct location. Post #23 with Aircraft.cfg shows: ..\Flight Simulator 9\Aircraft\AI-Mi8T_SBAI\ Post #24 with the texture bitmap shows: ..\FS9\SBAI_Mi-8T\ The aircraft.cfg file you posted earlier has a suitable path to a texture file. What files are actually in ..\Flight Simulator 9\Aircraft\AI-Mi8T_SBAI\texture.HuAF_MH86_705 ? D

Hi. I think the model and it's folder structure must have been ok because it showed up in Alex's screenshot in post #22. I'm fairly sure the problem was related to textures. Either the texture folder has the wrong name or, more likely in light of Alex's post #31, the texture files for that model are all incorrectly named. Judging by the same post, it also looks as though reistallation has messed up the path to the correct model file. Has flight 705 disappeared entirely now or does the grey helicopter still show up? D

Got it. Thank you: [fltsim.244] title=SBAI_Mi-17_HuAF_MH86_705 sim=Mi8 model=8M/a2-pz-lpg texture=HuAF_MH86_705 atc_airline=HUNGARIAN AIR FORCE ui_manufacturer=SBAI prop_anim_ratio=-1.52 ui_type=Mil Mi-17 ui_variation=Hungarian Air Force, MH86, Szolnok, 705 description=AI Mil Mi-17V5 model With realistic takeoff and landing designed by Sergey Bunevich\nFlight Dynamics correction by A.Fedotov for AI-Traffic use ONLY! atc_parking_types=Mil_Combat atc_parking_codes=MH86 *** Is the texture folder definitely called texture.HuAF_MH86_705 Do the textures themselves have the correct names? D

I'm sorry, Alex. What I meant was... could you post the aircraft.cfg entry for flight 705, just as you did a few days ago for 3304. Also, the name of the folder that contains the textures for 705 is probably sufficient right now. D

Hi Alex. Please forgive me: I don't like using my email address in forums. It's best if you just copy the [flightsim.xx] for 705 and tell us the path to the folder that contains the texture files. D

Hi. The model does appear for flight 705 so the problem is not anything to do with the flightplan or with the model: both of those are working correctly. I believe that the problem is that while FS can find texture 3304, it isn't able to find texture 705. The two most likely causes are: 1. that the relevant entry in aircraft.cfg is not pointing to the correct texture folder. 2. the texture files for 705 are damaged or are not named correctly. Could you please post the [flightsim.XX] entries in aircraft.cfg for the second set, 2- / 701/702/703/704/705 / + CFG TXT If possible, it would help if you could also tell us the path to the texture folder (for example C:\FS2004\Aircraft\SBAI Mi-8\Texture.705) Cheers, D

Hi Scott. If you have Traffic Tools installed correctly then clicking the Help dropdown menu should open a document that describes the ins & outs of the three files required for making a flightplan. Given your comment above, I guess you've found it. The section about the structure of flightplans.txt and the section on setting times & dates are a very useful reference. The compiler will handle flightplans that span several days perfectly well, and FS9 is equally happy with the resulting bgl. Concerning your question about the odd 35 seconds, I've always thought it's just some strange aberration in the compiler, possibly something to do with the way the turnaround time is implemented. You can have fixed times for arrival & departure (insert an @ in the appropriate place) or have the compiler set the arrival times according to the aircraft's cruise speed defined in the aircraft.txt document. Once you've got your head around the flightplans.txt structure, very small flightplan bgls up to half a dozen legs and two or three discrete plans, are easily created as three documents in notepad and then compiled. I find my brain lasts longer if I create each leg on a new line and only join things up immediately before compiling. If you want to do a complete airline then doing so manually is more than a little daunting and AIFP is your very best friend. D

Hi. I guess you're trying to decide between a PC upgrade plus MSFS or X-Plane plus some addons plus a lot of learning. I guess you know the score with MSFS in that you are happy that all it will take is a hardware upgrade. Concerning X-Plane, although I never took it any further I tried the demo in 2020 and loved everything about it except ATC, poor AI traffic and... the unfamiliar user interface & controls. I think you might be better equipped to decide between the two sims after posting questions specific to X-Plane in the sub-forum, especially where addons, the UI or shortcuts are concerned. Of course, if you make the hardware upgrade, your PC will run both and there's nothing to stop you enjoying the eye-candy in MSFS while continuing to learn in X-Plane. D

I think a lot of FS9ers on Win 10 would disagree with you Bill.

This thread is getting longer than my memory. Scraping the barrel... I can't remember if you've tried running FS9 with Norton & Defender both switched off. -- edit -- A further thought, and probably a bit more useful: "New PC has HDMI output only: I had to buy an adapter in order to use it with my existing 1920 x 1080 monitor, which is very old and only has VGA input." Could this be the source of the fault? It does seem like something isn't updating automatically, and only when you force a window refresh. It's a hopelessly long shot but can you borrow a HDMI monitor for a test and connect it directly to your PC? Or fit an old graphics card to your PC?

I think it would be a very good idea to try FS9 with Norton disabled (and Defender as well should Win10 do a dirty and turn it back on automatically when Norton is disabled). Not even a straightforward 2D thing either then. Just no updates in the main 2D view until you force a redraw? That sort of confirms that the fault isn't in FS9. How does 2D work in full-screen? Is your new machine PC & monitor? Can you try a different type of output from the PC, I mean such as DP instead of HDMI, or even VGA? Is it onboard graphics? I couldn't find a reference. I hesitate to suggest this as your folder structure was obviously deliberately chosen but, if no solution presents itself, it might be worth considering another location, perhaps on C:\ D

Mine runs as admin as a matter of course; running without was never tested. I never found compatibility was necessary so that's never been enabled. Each configured differently for different purposes I guess. Pretty much what I'd found too. I think an all-in-one port from an old system makes finding such problems more difficult. I was lucky in that sense: folder structure in the new installation was very different to my original so a direct port wasn't possible. I'm glad it's working. D

I'm inclined to believe that as one installation works then the problem must be in the other installation and not Win 10. But... we all know how Win10 can behave. When my XP PC died and I built a Win 10 machine, I had a backup and ported FS9 piecemeal from that into a new folder structure in the new machine. I had no issues other than a few installers failing to run so a few planes were left behind. After a long struggle to repair the damage done by MS's fall creators' update, I took Winaero and prevented MS from pushing any further 'upgrades' onto the OS. Anyhow, after however many years I still despise the OS even though it no longer causes me any problems: it's ugly and has required dozens of registry and policy tweaks and has not had a major update since sometime in 2020. Whatever, enough of my whining... To the issue. On the assumption that it's not Win10 per se, in the still-uncooperative installation, have you tried cutting down your scenery.cfg in notepad to the bare essential layers only, and disabling fs9.cfg to allow fs to rebuild it? That may at least let it launch properly so that you can start adding stuff back in. D (if you haven't, and decide to try it, don't forget the backup ;) )

Assuming the popup panels that work in VC still fail to work in 2d, it must be a fault related to the view. Given that the gauges update whenever the view is refreshed, that does suggest the fault is something external to FS9. Perhaps something is only running on demand when it should be running constantly, though that doesn't explain why it only happens in the 2d view. Can you pull up a second window inside the VC? It's the [ key or the ] key by default. Does the fault persist in the secondary window while VC & popups work ok? It could be something simple like a .dll that needs an update but then it's a new installation of OS & sim so they should all be up to date. "... running on demand when it should be running constantly" or only running when it's permitted? Without wanting to seem condescending, have you tried disabling your anti-virus? Beyond that, I'm out of ideas but there must be someone here who has a grasp of graphics & display drivers. D

It may depend on what else you have installed. Some more stuff to think about... Is your new FS9 installation still vanilla (I guess yes because I think all stock planes have a VC)? Have you installed any addon planes (I guess as above)? All gauges? All planes? Does other stuff in 2d panels update correctly on the fly (thinking throttle, mixture, flaps, trim wheel & caps)? Are you running FS9 in parallel with or linked to any other apps? Do you still have Defender running? What happens to gauges in popup panels when you're using the VC (might narrow down to gauge rather than panel rather than view)? Is the GPS's moving map working correctly? Have you rebuilt FS9.cfg? Or is your current copy one that's ported from a backup of your old installation? D

I know nothing about debugging software or processes and imagine anyway that you'd need a healthy setup for comparison. Fifteen or so years ago I used to make occasional use of Microsoft's sysinternals site: https://docs.microsoft.com/en-us/sysinternals/downloads/process-utilities There may be something useful there but that low level stuff is beyond me now. Out of interest, what OS have you installed? If you have Win 10, do a few FS window changes and then take a look for errors in Event Viewer. Also, did you manually install any versions of .net? D

FS9 Jim. TBH, that probably doesn't either...

DX12 at home. Could be a .net thing, too.

Hi. It does sound to me like a driver problem but can I suggest you disable your fs9.cfg and let FS9 build a new one, just to be sure it's not some obscure configuration problem internal to FS9? Also, I just did a 5 second search for DX10. Am I right in thinking that if it has the preview option, then it's an incomplete version? You could try a different version though I can't make a suggestion -- I'm at work and have no idea which one I have at home... D

Hi. Well, I just read this article and have a couple of questions, more or less the same thing. From a non-flying perspective and ignorant of reasons for the way things are done, using the controls' primary characteristics on final seems more sensible. So, considering the basic: a normally aspirated engine & fixed pitch prop... First, aside from history & tradition, why *are* the secondary effects of controls used on approach? Is it just a carry-over from the cruise where a plane is trimmed for the preferred speed and then a more easily adjusted throttle is used to control vertical speed? Second, in the section 'Getting practical', the author writes "... flying final approach like you're on an ILS, that is, holding speed with throttle and height with pitch" so, if it really is normal practice on instrument approaches, why isn't it also done on visual approaches? What difference in circumstances requires one method in preference to the other? D

Hi Richie. Broadly, it's specific to each radio stack and the preference of whoever created it. Some have click spots on the knobs, outer ring for digits left of the decimal, inner ring for digits right of the decimal. Sometimes adjustment is done on the display digits or the gauge itself. Sometimes you can scroll, sometimes you have to click + drag, sometimes just keep clicking. Sometimes L mouse button is decrease and R button is increase, and sometimes it's left or right side of the knob... As you've found, the difficulty is compounded by the lack of instructions with any given panel and the fact that very often there are non-working dummy knobs & switches just for the sake of an authentic appearance. If there's a specific panel or gauge that's giving difficulty, post a screenshot & a question specific to that panel. Someone here will know how to use it. D

Hi. If your Thrustmaster doesn't have a gate on the throttle lever, you'll have to assign a real button to the function or use the keyboard. I have a Saitek quadrant with the necessary, and a Black Widow vibrating monstrosity that doesn't. With the latter, I've assigned a keyboard press to the function instead. Do it like this: Load a flight. Set throttle levers to mid point so that Reverse is not active. Open FSUIPC. Pull up the Buttons + Switches tab. Fields should all be blank: Drag back your throttle lever through the gate. When the button activates, some FSUIPC fields will populate. Across the top you'll see 'Choose the action for this button...' Put a tick in 'Select for FS control' In the drop-down box for 'Control sent when button pressed', choose 'Throttle Decr' Put a tick in 'Control to repeat while held' And in the 'Control sent when button released' drop-down box, choose 'Throttle Cut' Click OK... You can use any joystick button but obviously, if you've got gate & button built into the lever... Also, you can assign a different button to each engine or, if you don't have enough levers, you can assign one button to control all engines. If you want to use the keyboard, use the Key Presses tab, though to be honest if you're using the keyboard you may as well just use FS9's Decrease Throttle setting. Click 'Set' in the left half of the pane. The text box should then show 'PRESS KEY' Do your key combination and as above, choose Throttle Decr and Throttle Cut. Click Confirm Click OK

If you're not in any hurry, it might be worth considering this: The corresponding yoke has received negligible criticism; some stiffness in the shaft seems to be all that's reported. If the proposed quadrant is built to the same standard and from similar materials then it may be worth waiting for. On the other hand, it could be a long wait. There have been some problems in obtaining parts for the yokes so a lot of yoke pre-orders were delayed. D

As I recall, it's in the Buttons assignment tab of FSUIPC. The reverse thrust function on my (Saitek) quadrant is actually a button built into the lever's end of travel beyond the gate. I'm at work right now. I'll post a longer reply when I get home. D

Hi. You can extend the battery life with FSUIPC. (Or get a few extra minutes by adding a few extra volts to the battery. Under [Electrical] in aircraft.cfg, change max_battery_voltage=24 to max_battery_voltage=38) D