TheRedBadger

I could see that as a possibility. I never changed those settings (if they exist) and I know I’ve reset the computer before. I know there’s a 4GB patch for the sim, I don’t know if it’s what I need or if I can actually allocate that much to the simulator. My computer has 8 GB of ram available, the sim was using just 1.3MB last I checked at its peak, yesterday (that was 70% of the ram which is odd that it wasn’t 35% of 4). I have a 64-bit system. Actually this is “regular ram” right? We aren’t talking VRAM are we? Because there I think I only have 2 GB (or half of whatever FS2020 needs).

Tested it a little more. Even from a relatively far distance (10 miles), the simulator gets slow anytime I'm looking at scenery, no matter how simple it may be (a small, local scenery, or a big, payware DFW-esque scenery). Tried default IAH and the sim works just fine... Added the afcad for IAH without the scenery and texture folders and it still works fine. I feel this has something to do with any type of addon textures, but I don't know /what/ it is... -Removed all static object libraries (no use) -Re-installed the texture folder in the main directory too, but no use

Nah no antivirus at all. Size does matter as my AUS scenery is ok, but not JFK or SEA (which definitely shouldn't have been a "low FRF" airport). Nothing unusual on task manager. The usual google pages and discord running, but nothing out of the ordinary. The sim used to run just fine with those active. Setting the mips to 1 doesn't make the sim any better. Obviously I could just set all the things to 0 and the sim works fine, but the problem is I know my computer has been able to handle much more before without issue.

I had my computer reset (windows 10), reinstalled the sim and all. Seems like at any addon major airport I'm at the frame rates take a huge hit when staring at certain areas. Before even my FSDT sceneries would work just fine and with lots of traffic. Only a select few airports I considered to be "frame-rate heavy" before this reset. Right now I have my FSDT sceneries with light traffic and they just can't take it without stuttering so hard sometimes. Zero traffic the problem persists. I feel like maybe it has to do with how my stuff is installed into my simulator but I don't know how. The display settings I've never toyed with very much and they're 90% the same. It's never made a difference. I do have a lot of static object libraries folders installed in the addon scenery library, as well as some textures installed in "flightsimular9/textures" as required already. Should they instead be somewhere else?

Older thread, but I ran into this problem when reinstalling the sim and wish I had posted my solution more explicitly. The original problem was that the pedals, upon being depressed, would result in some partial braking remaining (confirmed due to reduced takeoff performance), and the image "brakes" remaining on the bottom. Differential braking no longer observed, but some residual braking remained. Rudder pedals both checked for "reverse" in the joystick axes page. The fix was to increase the sensitivity all the way to the right for the "left brake" and "right brake". Null axes could be adjusted as necessary, though the real culprit was sensitivity, as reducing it anything less than full caused residual braking to remain. Of course, the logitech joystick and rudder pedals' assignments must not be shared, and each "shared" assignment must be removed from one (i.e., remove pedals from affecting aileron axis).

I tried a full reinstall and only installed any FSDT scenery right after. Unless certain things aren’t quite uninstalled..

How can I not worry when it got you nowhere :confused: ? Heck if I could install all those files without having to go through the registration crud that'd be great. I wonder if that's the big culprit behind it. Kinda wish those sceneries were like other paywares where you verify your transaction in the executable, get the files, install it and that's it. Not "install then register in the sim". Just causes a lot of trouble. I understand it's because of demos but certainly you could have a "demo only" addon that doesn't screw with confirmed buyers. Just some feedback, I digress. For now I'll have to settle on other addons until I decide it's time to try a full computer reinstall which is going to HURT so much backing up everything and hoping I don't make it worse. I did spend decent money on those and I don't want to give up and request a refund.

Hmm you can whitelist a file? Heck I don't even know if I have an antivirus on my computer :) . I do have my entire simulator "whitelisted" under some security settings on my computer. I forget what. Seems kind of outdated for me as this references an older version of FSDT when they worked with esellerate. Cloud9 is a foreign language to me :l . I'm also only installing a single scenery at a time. The buffer overrun issue with LAX no longer persists; it just crashes on boot like every other scenery.

Hi y’all. This is related to the FSDreamteam sceneries. I’d already spent about a week with the help of Umberto on their site, but it seems even he’s not sure what to do next. Without going into grinding details, the simulator crashes anytime a FSDT scenery is installed during boot. We tried several fixes like ensuring FS9.1 and the noCD patch are installed correctly in the right order, as well as downloading their addon manager. A complete reinstall of the simulator yields the same crash on boot. It is installed in my C: directory, outside of program files (same way I have done it for years). I have windows 10. C:/flight simulator 9 The event viewer references the “bglman.dll” file in modules as the source of the crash. %%%%%%%%% When testing with the LAX scenery (I have others), I get a special “buffer overrun error” and it crashes though we haven’t investigated this very much and I have to confirm again. I am not sure if this is affecting the other sceneries as well. Note the sceneries (except LAX) we’re all working well up until flying into LAX that I noticed the airport was now “in trial version”. Attempting to register the key resulted in that same overrun error which affected all other sceneries from then on. But not sure how. For now I’m isolating this as a separate issue, but perhaps I should look into it more. %%%%%%%% Thoughts? Thanks!

Aaaaaaaaaaaaaaaand I found the answer. Frankly I'm upset I did not try this earlier as I had seen it mentioned on another forum but... am stubborn. So much time burnt.. Just remove/delete the BACKUP folder in the flight simulator directory and that somehow does the trick. I had a hard time finding explicit answers for my troubles so at least now it's in plain english: "fs9.1 already installed" when it ain't simply means delete the dang BACKUP folder!!

Have been troubleshooting my sim for the past 3 days after an FSDT scenery was giving me registration problems and I had to do a reinstall /twice/ since I could not get the thing to even load at one point. The first time I uninstalled FS9, reinstalled it, then uninstalled 9.1 and then reinstalled it again to make sure it was done right. I had to uninstall fs9 again because of an issue with the nocd patch, so it wouldn't even load, or if it did, it would load the splash and then quit. The second time I uninstalled fs9.1 /before/ I uninstalled fs9, and now when I try to actually install fs9.1, the system tells me it's "already installed" and will quit. That's not what such FSDT scenery is telling me (tells me I need 9.1 and that I'm using some old .dll for fs9.0). I don't have the uninstaller available on the fs9 directory so I either do something either more complicated and break the simulator again, or I try to do it the right way. Thoughts? What should've been a 10-minute problem has swelled into a major a headache. Thanks!

The entire computer black-screens while sound continues in the background, the screen appears to "turn off" before a bunch of broken video appears, blacks out, then re-appears repeatedly. It's been quite a long time since I had this type of crash happen and I thought I was through with it. I can't remember how I fixed it. It may have been a complete re-install and then deciding to keep sceneries installed to a minimum, though that clearly isn't doing me much help (I may need to clean up). Having said that, if the problem is the computer's lack of capabilities, I'm considering an upgrade since this computer is now 10 years old (XPS 8000 something, i7, can almost run MSFS minimum except for lack of video ram), but I'm concerned I will still run into this problem even with an advanced computer, and I'm not going to cough up a lot of money if that extra performance means I'll still be smashing my keyboard in a fit of rage :mad: ! Thoughts? Or is FS9 arguably "prone to crash" itself or any computer just due to its.... design?

I assume you're referring to the fact that a lot of AI repainters have retired from making FS9 files for their works. Thankfully I've been able to convert a lot of FSX stuff for FS9 use, but even then, you can't convert entire models to another sim. Oh and then there's the fact about "dead links", so flyingcarpet and borisrepaints may no longer be accessible. I can relate What repaints are you looking for?

All the time still, for the past 8 years now. Plenty of addons, plenty of "world building". With MSFS it's all built for you already though which is very nice.. I'd certainly love if the default sceneries were better, but that's why they're default sceneries. Most of the time I just download an addon and am happy with it. I doubt MSFS can be tweaked when models, sceneries and whatnot aren't up to par.

Thanks for the help! What I meant to ask is if the 3D graphics card of 1009MB is enough since the specs says it needs 1024 MB on the graphics card.

I've had and do have that same nonsense with FS"real"WX. That and the engine loads incorrect weather for a particular airport once the airplane is close enough to get an ATIS. Like, the engine says the metar for MCI is "strong winds north", but then the ATIS goes on to say the winds are westerly and my flight plan is ruined because I had planned on arriving to the north... Also stratus clouds disappear when you fly above the ceiling, but I think that's FS9. Considering getting FS global. My computer says I have 1009MB, and the website says I need 1024MB. Costing $40, will the engine not run or not run right?

Alright I've got it. I used MSPaint this time (likely what I used the first time) and it worked on the sim. Though I definitely am curious (and worried) about doing a little more than changing regs. I'm worried of getting addicted to too little, relatively meaningless changes. Thanks yall!

Oh right. I think I may have used MS Paint the first time. I have one question but I might be able to solve it myself if I just tried it... You mention a "straight save" on Paint.net or the editor. Do I not need to save it before it loads to DXTBmp? Again I woul dhave to try for myself and figure it out.

Yeah seriously. It almost feels like they just took the flight dynamics and specs for a 787 and crammed them into the a220. It's free so I can't complain but it's not "free" the moment I spend HOURS trying to fix things. I appreciate the work they put in, but I'd rather people not "lure" a stubborn fool like me to trying to fix awkward aircraft. I hadn't touched this in a while because of that fact alone; I spent so much of my free time off from work wasting it tirelessly with little success. Even now it's not the best aircraft I've got. Sorry for not responding. I just chose I couldn't look at this plane for a while else do this til the day I die. I'm definitely interested in your work, Senore Kirchstein! And appreciate the time you took to take care of this.

Adding to a list of things I have unresolved and unprioritized (next to the a220's flight dynamics and G5 gauge troubles) is how on earth do I (and did I) repaint the registration number on aircraft? I had done this correctly once but I just can't remember. I recently got the final result I wanted on paint.net, but when I open the aircraft on FS2004, the textures are blanked out!! Here was my process: 1. Cover up the old registration by copying some "white stuff" on the fuselage and pasting it over the old ones. 2. Type the new ones (gosh this is a pain). 3. Select the pixels and resize as necessary. 4. Save. I wish it was as simple as Microsoft Paint where the final result you see is what you get, but it's overcomplicated with all this "layering", transparency, etc. Maybe it worked the first time because I used an original texture the first time, and the second time I used the "modified" textures as my template?

Hi y'all. Have done a lot of fixing on their a220 model (including fixing the ridiculous weights, fuel flow, wingspan, etc. Looks like a 787's flight specs and weight). Unfortunately I can't fix the contact points. Sitting on the ground the dang aircraft is shaking violently. Wasn't there before, likely a byproduct of me fixing the weights to the real ones. Here's what I've got. I've tried toying with it (the damping ratio of the nosegear especially) but it makes no difference. point.0= 1, 54.420, 0.00, -8.1, 1181.100, 0, 3.500, 70.0, 0.5, 2.5, 0.99, 15.0, 15.0, 0, 0.0, 0.0 point.1= 1, -10.500, -12.00, -8.5, 1574.800, 1, 3.167, 0.0, 1.0, 2.5, 0.8100, 15.0, 15.0, 2, 0.0, 0.0 point.2= 1, -10.500, 12.00, -8.5, 1574.800, 2, 3.167, 0.0, 1.0, 2.5, 0.8100, 15.0, 15.0, 3, 0.0, 0.0 You'd probably need the whole model to test it but I really just need ugidance on what could be causing the problem. Thanks!

Hi y'all. Have done a lot of fixing on their a220 model (including fixing the ridiculous weights, fuel flow, wingspan, etc. Looks like a 787's flight specs and weight). Unfortunately I can't fix the contact points. Sitting on the ground the dang aircraft is shaking violently. Wasn't there before, likely a byproduct of me fixing the weights to the real ones. Here's what I've got. I've tried toying with it (the damping ratio of the nosegear especially) but it makes no difference. point.0= 1, 54.420, 0.00, -8.1, 1181.100, 0, 3.500, 70.0, 0.5, 2.5, 0.99, 15.0, 15.0, 0, 0.0, 0.0 point.1= 1, -10.500, -12.00, -8.5, 1574.800, 1, 3.167, 0.0, 1.0, 2.5, 0.8100, 15.0, 15.0, 2, 0.0, 0.0 point.2= 1, -10.500, 12.00, -8.5, 1574.800, 2, 3.167, 0.0, 1.0, 2.5, 0.8100, 15.0, 15.0, 3, 0.0, 0.0 Thanks!