falconluan

I've used it in FSX with DX10 mode for sometime. Only used the level function to improve the contrast, which has NO frame impact I think. However, it crashes FSX recently, don't know why though. Tried with default planes in default scenery, still crashes at random time. Seems that PMDG NGX can survive a little longer, maybe 1 hour or so.

For those who are using or interested in facetracknoIR, one of the dev has been developing another similar program named open track. The latest version is 2.3 beta. It supports multi track methods too, among them, the paper marker tracker -- aruco tracker is very promising.

I had exactly the same landing light problem yesterday. However, after I went through again every option of DX10 controller, the problem is gone. I think it's "lights\effects" who fixed the problem. So, yes, DX10 fixer CAN fix this! Pity that it is not available any more ...

I like this more than the FAA book: http://avstop.com/ac/flighttrainghandbook/index.html A little old than the FAA book though, but I like its accent, not as formal as FAA book, a little more fun to read.

The third night of ASN trial and I'm totally sold. Works like a charm on my rig, no stutters, FPS is on par with other weather engines. Was trying to test turbulence last night, so I used the searching function and chose an area was raining and had some wind. After loading, it turned out that there was actually a light to med thunderstorm! Like others said, the weather of fsx world has never been so thrilled!The visiability changing when near or enter or out a cloud; The excelent simulated turbulence, the awsome sound and texture of lighting(REX4 texture direct has credit of them apparently), I think I can't fly without it from now on. Great great work you ASN guys. :Applause: Nowadays we have a lot of really great addons for fsx which improve lots aspect of the old yet trusted (at least to me :biggrin: ) sim. For scenary, we have orbx, flightbeam, aerosoft and other brillant teams; For planes, PMDG, Realair, A2A, Majestic, LHC (I like their pacer) and so on; For textures, REX all the time; For weather, we have active sky series, OPUS, FSGRW; They all have done some innovatition jobs and worked around lots of fsx limits and raised the bar with almost every release. However, some aspects of fsx seem to be left a bit far behind, like ATC, AI and others. For ATC, maybe the VATSIM is to be blamed, since lots of you guys fly on it and no need for ATC addon at all! Just joking. I like the appearance ot ProATCX, I know there are a lot issues about it, but at least it is one of the rare ATC addons being developed right now. It will be great if innovation work had been done just like ASN and REX4 and I believe the market potential is as good as them too. For AI, again, VATSIM is to be blamed :biggrin: . Only MyTrafficX and Orbx AI get some update now and then. And it would be GREAT if there is a polished, easy to use, intelligent (fly some STARs/SIDs at least) addon for that. P3D seems to be rasing well at present, maybe it will bring more attention to this hobby and bring some effect on the dark aspects of flight sim as well. We'll see. :wink:

Interesting I just made a video of landing on one engine in this baby last weekend, not sure that if you can access this site though. Landing: http://v.youku.com/v_show/id_XNTgyODczNzAw.html engine failure after Vyse: http://v.youku.com/v_show/id_XNTgyODc3MjUy.html As you can see, I simulated the engine failure simply by retarding its mixture lever, it's kind of harsh I think and it's hard to regain control really smoothly. Also, I'd avoid the second notch of flaps when SE landing, cuz with that, you can fall below Vmc reaaal easy ^_^

hi j.c. I think I can only answer this one for now. It does not need a lot of rudder input during turns to keep it coordinated, a lot less than what you need in realair planes. I'm NOT saying that realair plane's FDE is wrong, just using them as a reference. As for your second and third questions, I almost flown in VFR conditions and not higher than 3000ft these days, so I can't answer you right now, but I can check it later and report you back.

I second that the Milviz C310R is currently the best piston twin for FSX. After cross comparing the C310, Milviz B55 and the duke, I decided using the 310 as my practicing twin, it simply just has a soul! The sound is amazzzing, the gauges are classic and beautiful, and to me the most important the FDE is stable AND active. I don't like the feeling of B55, it is a bit touchy/light like the most of Carenado planes, especially for the pitch control. It's really hard to control the vertical speed smoothy and steady. Maybe it is because my joystick is crap but I don't have such problem with the 310R, duke, pacer, lagecy, scout or other planes.

Is the LHC pacer the only GA plane at present which can response to cross wind during taking off and landing?

scenary complexity, orbx usually suggests leaving it at very dense, however, I found it hurts fps a lot on my machine, more impact than autogen...

While both RealAir and A2A's 172 have not come out, Legacy is the best choice you have. Also, I don't think the Legacy has to be "fast" or "very fast". Just leave your gear down and limit the manifold pressure within a lower range, you have a perfect "slow" IFR platform ^_^

If you already bought the RealAir Legacy, don't bother with another plane, leave the gear down, manfold presure under 18inch, restrict airspeed under 130knot, you'll get a rocky IFR training plane!

^_^

I can't agree RealAir more on this. As a PC sim, in FSX we have much less feed back than in real planes. So it is a trade off and balance. If planes in FSX are designed to be behave exactly the same way as real ones, they will be much more difficult to fly. Lacking the force feed back from the stick and rudder, the G force on your body, we as sim pilots depend very heavily on what we see and hear. The result will be slow response to the control and overcontrol tendency. Guys in RealAir are well aware of this and I think Rob has mentioned more than once here they want to make their planes "as real as possible" from a sim's view point. And I think that is why we feel their planes to be right and comfortable. What is more, they've made their best to overcome the lack of feed back by putting lots of graphics and sound effect to the Lagacy such as stall bufflet, slip sound etc. I like the slip sound best since it is hard and no realistic to make turns by staring the turn coordinator.

I think the upcoming Realair 172 will address that :Party:

+1 on "Stick and Rudder" I've been reading it for some time and it is really a great book. Some points of it: AOA is the most important thing of flight. Rudder is only to mend the fault left by designer The "glide line" concept for glide/descend path judge and control How to land a tail dragger

I have the same blurry issue on my low end PC too.I think it is related by slow CPU or bad state HDD(an enterprise class one, stable, but not fast).It seems like the texture does not have enough time to be loaded.So, I highly suggest you to play with this tweak:FIBER_FRAME_TIME_FRACTION=0.5This value controls the time which is used to process fiber, default is 0.33.Decrease this will gain you better fps, but more blurries, increase this will do the contray.Give a shot on this and check if it can get rid of your blurry, good luck!I have the same blurry issue on my low end PC too.I think it is related by slow CPU or bad state HDD(an enterprise class one, stable, but not fast).It seems like the texture does not have enough time to be loaded.So, I highly suggest you to play with this tweak:FIBER_FRAME_TIME_FRACTION=0.5This value controls the time which is used to process fiber, default is 0.33.Decrease this will gain you better fps, but more blurries, increase this will do the contray.Give a shot on this and check if it can get rid of your blurry, good luck!

I'm using an old logitech R100 steering wheel as the rudder pedals. It has a single axis for both throttle and brake, which is just fine as rudder control. Not has toe brake though but hey, it costs almost nothing, what more can we expect?

Yes, I know, using AM = 2 is meant to spare one core which can be used for face track.

The contents of this topic is mainly for those who:1) has a dual core CPU;2) want to use Orbx GA airports or similiar;3) want to use facetracknoIR instead of real trackIR4) is a GA guy (actually a combination of item 2 and 3)If you are the one, it may be worthy taking a few moment to read below:Here in this forum, quad core CPU is almost standard config these days, so there is little discussion on how to optimize FSX performance with dual core machines, unfortunately, my CPU is a dual core one ...I've tested the affinity task setting on a dual core rig and would like to share some finding.As we all know, in fsx, the fiber processing is fixed on core0, which can not be changed by AM values. AM setting can only 'move' other threads (such as texture loading) to other cores. Actually, I think the threads are not moved, they are simply prohibited. This is based on what I've observed:1) Affinity mask set to 2, in binary, is '10', meaning that the threads like texture loading on core0 are turned off, leaving those work to core1 only. From the CPU usage we can tell that core0 usage is not very high but many wild varies, while due to the non-stop texture loading work, core1 usage is always close to 100%.2) Back out the affinity mask setting, fsx acceleration supports muti-core CPU by default, we can see both core0 and core1 usage are close to 100%, indicating core0 also has a lot of work to deal with such as loading texture.These conclusions can also be confirmed using the "Resource monitor", a utility which is provided by win7.With AM = 2, the fsx disk access instance(I don't know the unit of them, threads?) is significantly less than the AM = 3 caseSo, we have to balance:AM = 2, core0 only processes fiber, a certain number of frame rate increase, but reduced ability to load texure, so there will be more blurries.AM = 3, core0 shares the task of loading textures, less blurries, but because of there is less CPU cycles to run fiber on core 0, frame rate is hurt.FacetracknoIR is also a CPU hogger more or less, if there is no AM ​​= 2 setting, both cores' load is fairly heavy so the face track will be very jumpy. While setting AM = 2, core0 load becomes lighter, we can specify facetracknoIR to run on core0 only, the whole CPU burden is balanced, resulting a smoother tracking experience, but sacrifices some texture loading ability.Also we can play with the FIBER_FRAME_TIME_FRACTION to give core0 more time to load texture, but have not tested it yet.Orbx cessnock YCNK is my favourate, little blurries, face track, works like charm. Of couse, I'm not familiar with fsx schduler machanism, all the above are base on my observation and bojote and others great efffort on the fsx tweak.Sorry for my bad English.

For me, the black screens after alt-tab shift can be restored by pressing "Enter" key.However, there are black screens after exit one flight and enter another one. "Enter" can not help on that one.