Jo Le Trembleur

Same here, with a Valve Index, and with the same graphics settings as the ones I used in 2.8 (stayed with MSAA 2X, didn't switch to DLSS, though I tried it too, but same issue with the huge dots).

Yes, you're right, I noticed this one too (TM Warthog).

Same here.

Just happened to me on Nevada, 25000ft, 350-400kts.

You're right, same here, also with Warthog. A little bit disturbing in the lower RPM range.

I just installed the 2.7 open beta this week, and I experienced exactly this, as mentioned by the OP : "Clouds jittering. They move about like they are a separate superimposed image & shake in the distance". This makes the clouds unusable (at least for me) in the current state. I'm using a Valve Index, by the way.

Hello, I'm trying to use the MOOSE Cargo system, but I don't seem to understand it correctly, unfortunately. What I'd like to do is just creating transportable troops with human-controlled helicopters, without using task dispatching or any other particular logic. It would be up to the players on the server to land near an infantry group, load it, transport it somewhere else, and unload it there. I read the documentation at https://flightcontrol-master.github.io/MOOSE_DOCS/Documentation/Cargo.Cargo.html, and after reading the following section: " 5.2) The #CARGO tag to create CARGO_GROUP objects: You can also use the #CARGO tag on group objects of the mission editor. For example, the following #CARGO naming in the group name of the object, will create a CARGO_GROUP object when the mission starts. Infantry #CARGO(T=Workmaterials,RR=500,NR=25) This will create a CARGO_GROUP object: with the group name Infantry #CARGO is of type Workmaterials will report when a carrier is within 500 meters will board to carriers when the carrier is within 500 meters from the cargo object will dissapear when the cargo is within 25 meters from the carrier during boarding So the overall syntax of the #CARGO naming tag and arguments are: GroupName #CARGO(T=CargoTypeName,RR=Range,NR=Range) T= Provide a text that contains the type name of the cargo object. This type name can be used to filter cargo within a SET_CARGO object. RR= Provide the minimal range in meters when the report to the carrier, and board to the carrier. Note that this option is optional, so can be omitted. The default value of the RR is 250 meters. NR= Provide the maximum range in meters when the cargo units will be boarded within the carrier during boarding. Note that this option is optional, so can be omitted. The default value of the RR is 10 meters." I thought I only had to name my infantry group with something like "USTroop01 #CARGO(T=Workmaterials,RR=500,NR=25)", for example, and then I would automatically get submenu options under the F10 menu for loading/unloading when my helicopter would be landed near enough. But I don't get any submenu under F10, so I guess my understanding is not correct (?) Would anyone be so kind as to help me achieve what I'm trying to do, please? Or maybe it's not possible and using task dispatching is mandatory? Thanks for your help, and sorry if I missed anything when searching the forum and documentation.

Thank you so much ED for all this hard work ! :thumbup:

As a froggy myself, I'd prefer the Rafale, or the M-2000-5, but in order to stick to the poll, I'll vote for the Fulcrum ;)

Nice job guys, many thanks ! :thumbup: Especially for this one : 'Corrected pilots eyes'. At last, I won't do nightmares anymore after flying the Gazelle and looking left in the cockpit. :D

Sorry, I lacked precision : It says 'Requires another product', but I can still add it to my basket too.

No, I double-checked, I was logged in. Odd if it's not symetrical with MiG-15 owners. Apache will probably find the right answer soon, I'll wait until then. Thanks Apache, and sorry if this causes you trouble :noexpression:

I've got the Sabre, and when I try to buy the campaign, it tells me it 'Needs another product'. Don't you get the same if you've got the MiG-15 ?

Thanks to you, Apache :) Looking forward to play it with the Sabre, possibly without having to buy the MiG-15.

The campaign has been published, but something's not clear to me : It says 'The DCS: MiG-15bis and DCS: F-86F Sabre are required to be installed and activated into the DCS World 1.5 for the campaign.' I thought only one of these planes was required. Was I wrong ? Any body has further information, please ?

Same thing. I may be wrong, but it seems to me it helps.

Same issue here : I made a mission with absolutely no wind, and the plane systematically deviates left at take-off, forcing to apply rudder right to stay aligned. I first thought there could be an issue with my Saitek rudder, but I checked the neutral in its properties, and it seems OK. Quite an odd behavior (?)

I did this, and logically it improved a little, but lateral skidding is still there when applying strong braking. I succeeded in staying aligned only by applying brakes very carefully, but my problem is now the length of the runway :smilewink: