Oh and by the way, there are no .crash files under /Ka50/temp directory after this happens.

Yes, as others have mentioned......if you are getting tearing, most likely vsynch is "OFF" on your video card. Set Vsynch to "on" and it will limit the FPS to your monitor refresh rate getting rid of any tearing.

I do know the difference and yes it's obvious a physics based FM is desireable over a scripted/"simple" one which is why I posted the thread. It would be a nice surprise if the dynamic FMs can be ported to replace the simple ones currently in existence. That's all. And that was my point so I disagree my post had no point. sorry.

"extreme regions are scripted"........

Ummm...there is. I guess more wishful thinking than a question. I'm sure ED would have done it if it was easy enough. My guess is the scripted FM has hooks into many other things that can't be easily changed.

Anyone else have this combo and getting BSOD on module wmxlcore.sys? Wmxlcore.sys is a logitech file so I'm leaning towards a Logitech problem, not a Win7 64bit problem but Blackshark is currently the only simulator I have the problem with. Was fine when I was running Vista 64..... Other sims like IL-2, ROF, Flaming Cliffs, FSX run without a hitch. If anyone has/had the same problem, please let me know if you found a fix. I've written Logitech support and they said they will look into it for LGS 5.09 release. thanks.

Of course there is a point and of course it will either happen or not.

I think I'm pretty sure I read they are not touching the existing FM but I wonder how difficult it would be to port the SU25T FM to the SU-25 and the A-10C FM to the A-10A.

Since one of them will have advanced physics based FM and the other a "scripted" FM engine, will they handle very differently? Just curious as I feel they should handle similarly without any loadout. I'm looking forward to the release of both projects. Cheers.

Thank you Frederf!

Hello, can someone please confirm the MD5 Checksum for the DCS-BS_Patch_1.0.1c_EN.exe patch file? I got the below. Just want to make sure before I patch. MD5 Checksum: 939CE8BF0604EA9872B8B5A38BB762C7 Thank you.

I also have the exact same question. I scoured through the forums but haven't found an answer to exactly what directories/files to backup and restore in case a rebuild is necessary. For example, what folders/files need to be backed up for pilot info/progress, hotas settings, and all other option settings? Thanks.

Thanks Panzertard!

Hi Panzertard, I went into options and deslected the new trimmer implementation but the variables were still missing in the FMOptions.lua. Can someone please check their FMOptions.lua file to see if the variable "HelicopterTrimmerMethod" exists? Thanks for your help.

I left the GUI setting alone in which the new standard is default. However, in the readme, it says: "The control deadzone for the new trimmer implementation can be adjusted in the following configuration file: ...Scripts\Aircrafts\_Common\FMOoptions.lua The relevant variables are: HelicopterTrimmerMethod - trimmer implementation option: 1 - original, 2 - new (selected by default)." but I don't see those variables in the file. So that is my question.....why don't I have the variable in the file that is described in the readme? Is this normal? Thanks.

Thanks. Below is the content of my FMOptions.lua. Do I need to add the line (trimmer implementation option = 2) somewhere? ----------- for new helicopter trimmer method ----------------------------------------------- ----------- (joystick will be disable after trim until it come to neutral zone) ------------- HelicopterTrimmerZonePitch = 0.05; HelicopterTrimmerZoneRoll = 0.05; HelicopterTrimmerZoneRudder = 0.1; ---------- for old helicopter trimmer method ------------------------------------------------ ----------- (aperiodic process) ------------------------------------------------------------ HelicopterTrimmerTauInverse = 7.0; --lower value - decrease trim speed after trim button release.

Guys, After the patch, I looked in ...Scripts\Aircrafts\_Common\ as the readme says but don't see a FMOoptions.lua. Is it a typo? ....because I do see a FMOptions.lua. in FMOptions.lua, I don't see the entry mentioned in the readme.....HelicopterTrimmerMethod - trimmer implementation option: 1 - original, 2 - new (selected by default). help appreciated. Thanks.

hmm... mine came out to: E5A1A4A431C25A1D8B2428066487FC45 ----------------------------------------------------------------------------------------------- UPDATE: Redownloaded and now I get the correct MD5 of 2925CD9F589D3D4ED3C8C685A4EA8BC0 Thanks!

Hello, can someone please post the MD5/checksum for the new patch? I want to make sure nothing is corrupted during download. Thank you.

Thank you guys. I don't understand why then they only give 10 deactivations. Shouldn't we be able to activate/deactivate as many times as we want as long as only 1 activation is valid at a time? Again, sorry if this has been discussed here before. I'm just in a hurry because I'm about to build and I won't have access to internet during that time. Thanks again.

Folks, Sorry if this question is already answered but I am building a new computer. Do I need to deactivate first on my old computer before building, installing, and activating on my new computer? Thank you.

They just released the Nieuport 17 yesterday. Awesome rotary engine airplane. Now we have a total of 5 high fidelity airplanes: Fokker DVII, Albatross DVa, Nieuport 28, Nieuport 17, and the Spad XIII. They are all awesome! Check out their website here if you haven't been there: http://riseofflight.com/

I have ROF now. It has some of the best, yes, best flight modeling of any simulator on the market today. Comes with 4 flyable aircraft with a lot of detail and more planes are coming since it is a modular design. There are a few rough edges but Neoqb is committed in evolving the product. I say if you want to fly an old WWI crate, ROF is the closest to the real thing IMO.

That's the maximum bandwidth. the actual sum of packets sent/received will be much less than that.