nikaslan

Also check if your audio driver is forcing some specific sample rate, 192 KHz for example. I had audio crackling when my Asus Xonar audio driver was forcing 192 KHz sample rate AND FSRealistic was enabled. When I did set the sample rate to 48 KHz the crackling stopped.

Well, I have to report that my issue has been resolved One thing I have missed till now was that the Heli Manager had the option to set your custom sensitivity settings. I had scrolled until the “Enable Engine Failures” option, didn’t understood that there was more below... In Realistic mode the "cyclic sensitivity" setting is set to 80%. Remember I talked about things like “this Bell 47 reacting too slowly to cyclic inputs” and “that it's needing larger cyclic motions to respond”? Well, the moment I set cyclic sensitivity to 100% these things suddenly disappeared! The heli became responsive and I can control it very precisely now. Hovering and landing in restricted spaces is confident and precise. Tail stability remained to 0 and Heli Stability to 5. Happy camper (and customer) now, I am leaving you to continue flying in the fjords 😛

Thanks for the tip regarding Flyinside's forums, didn't know about them, I will surely check there.

Having purchased the FlyInside Bell 47G a few days ago and tested it in MSFS, I can say that I have really mixed feelings, especially regarding its flight handling. I have flown many helicopters in X-Plane, Dreamfoil B407 and AS350 as well as the default R22 and 206, and Dodo 206 in FSX, and I have also been involved in creating and optimizing many flight models for HTR (Helicopter Total Realism) plugin for FSX. I also had a RL flight in an R22 some years ago, having got the controls for some of the time. Is it my idea or is this Bell 47 reacting too slowly to cyclic inputs? I mean, it seems it's reacting to inputs like it has much more inertia/mass than its size suggests. The effect is that it's needing larger cyclic motions to respond and that seems to make it difficult to control it precisely and many times I find myself overshooting in realistic mode. This happens even after I adjust both FSUIPC axes curves and the 47G cyclic settings in MSFS. I don't have this issue with any of the above mentioned helicopters. Even the Dreamfoil AS350, which is a handful, I can control and hover with extreme precision as it's pretty quick to respond to even minimal inputs. The Dreamfoil B407 is said to be 'spot on' in its handling by people who have many flight hours on the real thing, and the same goes for the Dodo B206. Is this seemingly 'sluggish' response indeed realistic for the Bell 47G? Is it because it's an old bird? Are all other helicopters overly quick to responses?

Yes, in advanced mode it is definitely better than the default FSX 206, but nowhere near the flight dynamics of the Dodosim 206 or even HTR-enhanced FSX helicopters. You can tell from the way it handles that it's in reality a plane modified to fly like a helicopter. And this is normal considering that there are no helicopter physics present in the sim currently. Considering that, the H135 is an amazing accomplishment on its own and our only option currently, that really flies quite well. Lets only hope the upcoming helicopter flight dynamics are at least on par with Dodosim 206 or X-Plane.. Having said that, I always prefer flying in X-Plane 11 when it comes to helicopters, or FSX-SE (DX10) both Dodosim 206 and others with HTR enabled.

Hey, isn't this the nag thread for rotorheads? I'm just nagging 😋

You can't have a proper Flight Simulator without simulating helicopters!! It would be against Microsoft's legacy, as helicopter simulation was a given in all recent releases at least. What a huge, tremendous lost opportunity, to have the entire world simulated like this and not be able to fly helicopters at all... I really, really hope they are adding them later on, providing realistic flight dynamics, on par with the new airplane flight modelling. It would be a huge disappointment and a game changer (pun intended) for me if they didn't.

Hi all, After upgrading to a new rig (9600K, 32GB RAM, gtx1070) I noticed that had more (!) stutters when panning around than with my previous rig, although I generally fps was way up. About a decade ago I had similar issues in FSX, which proved to be related to the screen refresh rate combined with the sim fps, when VSYNC was on. If I turned off VSYNC I had screen tearing when panning instead of stuttering. I solved it by internally limiting the sim FPS to 30 AND setting VSYNC to 1/2 monitor refresh rate (60/2). I did something similar to Xplane 11. I limited FPS to something like 30,5 or 31.5 in Nvidia Inspector AND set VSYNC to 1/2 monitor refresh rate (standard not adaptive). I also set "threaded optimization" to OFF after testing both options. And now I enjoy incredibly smooth panning at 30fps (Track IR) in Xplane, way smoother than FSX ever was.

If you are using DX10 Fixer with FSX-SE then I think only version 1 of Reshade is working. And then you have to rename the ReShade32.dll to d3d11.dll (at least I had to, in my system) for FSX-SE to start.

@ ckyliu I can feel you pain. In the old days of FSX Acceleration tweaking was a big part of the game. ENB made my FSX crash too. OOMs on the other hand were never an issue for me, I don't know why, maybe the my specific configuration and settings were never forcing the 32-bit software to its limits. But the truth is that I had frequent crashes (non OOM related). BUT, FSX-SE is another thing altogether. All basic tweaks and fixes are already applied, I only have Bufferpools=0 and that's it. Period. It's stable as a rock, it never OOM'ed me. Also, no more ENB but Reshade instead. I can switch from full screen to window like 100 times and it will never crash. The difference with Reshade is astonishing with the right preset! That's it. No tweaking, no pain. It just works as it should have from the start. As you already observed, I have enough A2A planes and the investment to switch to P3D, to gain what?, makes absolutely no sense to me. But I understand that everyone has different needs and experience, so YMMV.

In fact, with some minor investment you can easily get FSX-SE to P3D levels, visually at least. With Steve's DX10 fixer combined with Cloud Shadows you get virtual cockpit and cloud shadows. Also, If you invest some time to use Reshade (free) you get a really major upgrade in visual/lighting quality, way above anything vanilla P3D can produce, especially with some excellent presets (I use this one: https://sfx.thelazy.net/games/preset/4143/ ). Beyond visual improvements, you still have a 32-bit simulator. Known negatives aside, you get maximum compatibility with all great addons, without having to pay way more for 'academic' use. With ORBX Global, SA OLC and Vector I am currently on a great trip across Central and South America to Antarctica. Add to this the full REX texture treatment and AS2016 real-time weather, and I don't see FSX-SE going anywhere for the foreseeable future, not at least until XPlane can provide the same whole experience (ATC, weather, seasons, non-ortho terrain textures, vector accuracy) worldwide.

I don't think it's a graphics card issue, your card is pretty standard. As for FSX itself, do you have the boxed or the Steam version? What is the error message that you are getting?

I assume you use the DX10 fixer. Make sure you use the 32bit dll and rename it to d3d9.dll instead of dxgi.dll. It's not supposed to work this way for DX10, but it does. Happy camper. :smile:

I never had any luck with either SweetFX or ENB. Constant CTDs with both of them. And then I discovered ReShade. With MasterEffect ReBorn config I can get whatever ENB or SweetFX offered without a single CTD, plus on-the-fly :smile: changes.

IMO something that needs serious overhaul in FSX engine is helicopter flight dynamics. Helicopters in FSX behave totally unrealistic and only external code can save the day, which is the case with the Dodosim 206, the Aerosoft Huey and HTR (Helicopter Total Realism) module. As incomplete XPlane 10 feels in various areas, its helicopter flight dynamics are a dream come true. Coupled with some really great 3rd party models that exploit XPlane's potential to the max, there is simply no comparison in the helicopter department. I hope DTG moves in the right direction and enhances flight dynamics, especially for helicopters.

For many years I had been sticking with DX9, mainly due to better looking water. I had repeatedly tried ENB and SweetFX but both gave CTDs which totally ruined FSX for me. This was a no-go so I reverted to using just Shade, which didn't give the contrast and palette changes I wanted though. Sometime ago I heard about ReShade. Installed it along with MasterEffect ReBorn real-time effects and after some tinkering I was a very happy camper! No CTDs and great bloom, contrast and color palette control. Later I made the switch to DX10 using Steve's fixer. I continue to use ReShade with MasterEffect ReBorn along with Shade. Never had better looking water with wind dependent waves, and with palette contrast and coloring that rivals even X-Plane. Note however that the final outcome mainly depends on the ReShade configuration. It can make or break FSX looks.

No problem, I'm not in a hurry. :smile:

Hey, we better leave the two guys that transformed XP do their stuff together, shouldn't we? I'm drooling over a UHD NZ Pro ...

After testing with the world-models downloaded from your link the error is gone! Thank you! Another issue now :smile: : The texture used on the roofs of some buildings is a flickering 'tv static' or 'tv snow' effect that can be seen through aircraft. Here is a screenshot in Bodo (ENBO). Besides these minor issues, I have to point out that this is probably the most realistic country-wide scenery I have ever seen in X-Plane. Thank you Tony!

Affirmative Tony, I have the world-models-0.7.6.tar.bz2. I am re-downloading just to be sure.

Ok, I am probably doing something wrong but I get constantly the following errors with the alpha 2 release: 0:00:07.312 I/FLT: Init dat_p0 type:loc_tak apt:ENBO rwy:07 0:00:07.312 E/SCN: Failed to find resource 'objects/forests/trees/tree19m_1.obj', referenced from scenery package 'Custom Scenery/norway-pro/'. 0:00:07.312 E/SCN: Custom Scenery/norway-pro/Earth nav data/+60+010/+66+012.dsf: 0:00:07.312 E/SCN: Unable to locate object: objects/forests/trees/tree19m_1.obj 0:00:07.312 E/SCN: Failed to find resource 'objects/forests/trees/tree2.obj', referenced from scenery package 'Custom Scenery/norway-pro/'. 0:00:07.312 E/SCN: Custom Scenery/norway-pro/Earth nav data/+60+010/+66+012.dsf: 0:00:07.312 E/SCN: Unable to locate object: objects/forests/trees/tree2.obj 0:00:08.526 E/SCN: Failed to find resource 'objects/forests/trees/tree17m_1.obj', referenced from scenery package 'Custom Scenery/norway-pro/'. 0:00:08.526 E/SCN: Custom Scenery/norway-pro/Earth nav data/+60+010/+66+012.dsf: 0:00:08.526 E/SCN: Unable to locate object: objects/forests/trees/tree17m_1.obj 0:00:08.526 E/SCN: Failed to find resource 'objects/forests/trees/tree2.obj', referenced from scenery package 'Custom Scenery/norway-pro/'. 0:00:08.526 E/SCN: Custom Scenery/norway-pro/Earth nav data/+60+010/+66+014.dsf: 0:00:08.526 E/SCN: Unable to locate object: objects/forests/trees/tree2.obj 0:00:08.526 E/SCN: Failed to find resource 'objects/forests/trees/tree17m_1.obj', referenced from scenery package 'Custom Scenery/norway-pro/'. 0:00:08.526 E/SCN: Custom Scenery/norway-pro/Earth nav data/+60+010/+66+014.dsf: 0:00:08.526 E/SCN: Unable to locate object: objects/forests/trees/tree17m_1.obj 0:00:08.545 E/SCN: Failed to find resource 'objects/forests/trees/tree1.obj', referenced from scenery package 'Custom Scenery/norway-pro/'. 0:00:08.545 E/SCN: Custom Scenery/norway-pro/Earth nav data/+60+010/+66+014.dsf: 0:00:08.545 E/SCN: Unable to locate object: objects/forests/trees/tree1.obj 0:00:08.545 E/SCN: Failed to find resource 'objects/forests/trees/tree1.obj', referenced from scenery package 'Custom Scenery/norway-pro/'. 0:00:08.545 E/SCN: Custom Scenery/norway-pro/Earth nav data/+60+010/+66+012.dsf: 0:00:08.545 E/SCN: Unable to locate object: objects/forests/trees/tree1.obj 0:00:08.545 E/SCN: Failed to find resource 'objects/forests/trees/tree18m_1.obj', referenced from scenery package 'Custom Scenery/norway-pro/'. 0:00:08.545 E/SCN: Custom Scenery/norway-pro/Earth nav data/+60+010/+66+012.dsf: 0:00:08.545 E/SCN: Unable to locate object: objects/forests/trees/tree18m_1.obj 0:00:08.545 E/SCN: Failed to find resource 'objects/forests/trees/tree19m_1.obj', referenced from scenery package 'Custom Scenery/norway-pro/'. 0:00:08.545 E/SCN: Custom Scenery/norway-pro/Earth nav data/+60+010/+66+014.dsf: 0:00:08.545 E/SCN: Unable to locate object: objects/forests/trees/tree19m_1.obj 0:00:08.578 E/SCN: Failed to find resource 'objects/forests/trees/tree18m_1.obj', referenced from scenery package 'Custom Scenery/norway-pro/'. 0:00:08.578 E/SCN: Custom Scenery/norway-pro/Earth nav data/+60+010/+66+014.dsf: 0:00:08.578 E/SCN: Unable to locate object: objects/forests/trees/tree18m_1.obj 0:00:08.612 W/OBJ: The object Custom Scenery/norway-pro/houses/autogen/PL/res-mid/RES_23.77x19.39_c70.obj has an LOD starting at 8000.000000 that does not match the previous LOD. 0:00:09.079 I/SCN: DSF load time: 583766 for file Custom Scenery/norway-pro/Earth nav data/+60+010/+66+012.dsf (0 tris) 0:00:09.079 I/SCN: DSF load time: 601307 for file Custom Scenery/norway-pro/Earth nav data/+60+010/+66+014.dsf (0 tris) 0:00:09.178 I/SCN: DSF load time: 660133 for file Custom Scenery/zzz_uhd_global_scenery1/Earth nav data/+60+010/+68+012.dsf (40704 tris) 0:00:09.378 E/SCN: Failed to find resource 'objects/forests/trees/tree1.obj', referenced from scenery package 'Custom Scenery/norway-pro/'. 0:00:09.378 E/SCN: Custom Scenery/norway-pro/Earth nav data/+60+010/+68+014.dsf: 0:00:09.378 E/SCN: Unable to locate object: objects/forests/trees/tree1.obj 0:00:09.412 E/SCN: Failed to find resource 'objects/forests/trees/tree17m_1.obj', referenced from scenery package 'Custom Scenery/norway-pro/'. 0:00:09.412 E/SCN: Custom Scenery/norway-pro/Earth nav data/+60+010/+68+014.dsf: 0:00:09.412 E/SCN: Unable to locate object: objects/forests/trees/tree17m_1.obj 0:00:09.445 E/SCN: Failed to find resource 'objects/forests/trees/tree2.obj', referenced from scenery package 'Custom Scenery/norway-pro/'. 0:00:09.445 E/SCN: Custom Scenery/norway-pro/Earth nav data/+60+010/+68+014.dsf: 0:00:09.445 E/SCN: Unable to locate object: objects/forests/trees/tree2.obj 0:00:09.445 E/SCN: Failed to find resource 'objects/forests/trees/tree19m_1.obj', referenced from scenery package 'Custom Scenery/norway-pro/'. 0:00:09.445 E/SCN: Custom Scenery/norway-pro/Earth nav data/+60+010/+68+014.dsf: 0:00:09.445 E/SCN: Unable to locate object: objects/forests/trees/tree19m_1.obj 0:00:09.445 E/SCN: Failed to find resource 'objects/forests/trees/tree18m_1.obj', referenced from scenery package 'Custom Scenery/norway-pro/'. 0:00:09.445 E/SCN: Custom Scenery/norway-pro/Earth nav data/+60+010/+68+014.dsf: 0:00:09.445 E/SCN: Unable to locate object: objects/forests/trees/tree18m_1.obj 0:00:09.612 I/SCN: DSF load time: 252940 for file Custom Scenery/norway-pro/Earth nav data/+60+010/+68+014.dsf (0 tris) 0:00:13.645 I/SCN: DSF load time: 4569053 for file Custom Scenery/zzz_uhd_global_scenery1/Earth nav data/+60+010/+66+012.dsf (645301 tris) 0:00:14.912 E/SYS: +------------------------------------------------------------------------------- 0:00:14.912 E/SYS: | There was a problem loading the scenery package: 0:00:14.912 E/SYS: | Custom Scenery/norway-pro/ 0:00:14.912 E/SYS: | The scenery may not look correct. 0:00:14.912 E/SYS: | Please see the log.txt file for detailed error information. 0:00:14.912 E/SYS: | (io_dsf.cpp:686) 0:00:14.912 E/SYS: +------------------------------------------------------------------------------- The scenery loads eventually but it seems something's wrong. No such error occurred with the first release... Any idea?

I also use this combination to get what I regard as the most acceptable and performance friendly weather generation currently for X-Plane.

Tony, I can't thank you enough for this decision I don't have the disk space and energy to hunt for available photoscenery for every region want to fly, and I, personally, prefer the sharp default textures to the relatively blurry photoscenery. I have the impression that this is the case now for the majority of X-Plane users. Your decision acknowledges that and makes this kind of scenery a god-sent gift for us. Regarding world2xplane, another conflict I had found for the non photoscenery users, was the bush-lines that defined real-world terrain patches, but appeared out of space without photoscenery.

Or you can use the following modification which makes the default Beaver amphibian (that is with phantom wheels): http://forum.mistymoorings.com/index.php?topic=245.msg1651#msg1651

Ryan, Dreamfoil are actively working on an update for the AS350 that will address the control issues, by re-coding the stability augmentation to be compatible with the latest XP versions. In the meanwhile, open the Plane-Maker, go to 'Expert' -> 'VTOL or Helo Controls' and in the 'Extra Inputs for Props' tab change 'PITCH then ROLL cyclic' to 10.0 and 03.0 (defaults are 15.0 and 07.0 IIRC). You can change these values to whatever suits you best. Problem solved!