FragBum

As an observation, I get very similar results with the Mi8 and Gazelle and Huey. I tried both rolling left and rolling right from a hover and pulled the collective without correcting for torque change but staying within torque limits. On right roll torque pulled the nose to the left and as the aircraft rotated the nose went up and tail down. The Mi8 did the same thing but the magnitude and lag resulted in a less dramatic result. Whilst left roll the torque moment pulled the nose left and down initiating a kinda spiral descent manoeuvre. The Huey had similar results but with opposite effect for left and right roll. I tried at a slight maybe 5 deg and also at about 15 deg roll angles, have I missed something?

So to the Mi8 the KA50 and the Huey are equally easy to fly so I don't see your point.

I'd like to discuss this in more depth I'm away from home ATM but yes even perhaps in a separate thread. I wasn't saying it's perfect and understand that the team are reviewing the FM. Agree large increase in collective gives torque warning but shouldn't that cause rotor RPM to drop? Also auto-rotate your supposed to watch rotor RPM and keep it in check right. :D

Try the aerobatics servers you usually can get help on your specific airframe depending on time of day. Strictly no weapons policy applies essentially there a great place to get your flying including formation flying skills horned up. :thumbup:

Yes YAK or even the CE 2 very easy to fly.

Nothing wrong with scuba diving in the game room,.. but definitely on those barmy tropical days. :P:D Yes 4K again I haven't seen any hard data for the Radeon VII in DCS @ 4K I think the same sentiments apply the Radeon VII is a good card but at 4K it still generally gets piped at the post by the RTX 2080. Having said that I see in some reviews it does keep up with the RTX 2080 and in some cases allows more eye-candy, maybe because of faster RAM? Problem is would DCS being so CPU dependent allow the Radeon VII to be fully utilised? From what else I've gleaned on the interwebs the Radeon VII would have advantages for maybe video editing which might be acceptable at it's slightly lower cost compared to RTX 2080. Maybe wait for AMD Navi or even new nVidia offerings. Most people using the Radeon VII here seem happy enough with them though. Maybe people with Radeon VII GPUs running DCS at 4K could chime in with some first hand wisdom. Although I suspect either way more CPU grunt might be needed as well. :) :thumbup:

To be honest I don't have any hard data for the Radeon VII for VR I think it has potential but I have no experience with it. Other people with a 1070 seem to to get okay VR performance but then the whole DCS VR performance depends on CPU clock faster is better, GPU more grunt is better and RAM speed again faster is better. It would be great for Radeon VII VR users to chime in with their experience, I just can't currently afford to buy one to test it out at this time but I would love to. From reading various reviews the Radion VII is just piped at the post by 2080's and 1080Ti's but it also has some advantage in different scenarios. My main interest is whether the faster RAM and larger RAM capacity gives the Radeon VII an advantage in VR, It also has more shader units compared to the 2080 which again should benefit DCS VR. Sorry I just can't say yes or no at this time.

Sure but it still doesn't work, even to the point 3d party devs are having to develop their own implementation albeit on a flaky platform. Just saying.

Seriously though they had to bring out other modules YAK, FA-18 etc F16 to come, before they could fix well DCS world, everything they promised before, new maps before making the old ones complete or finished or even optimised not to mention netcode that would surely help multiplayer and multicrew and third party devs. And just now without fixing anything much a new air plane totally out of the blue. Seems we need new aircraft to take our mind off the other bits that are not getting fixed! Just an observation. Don't get me wrong I love DCS but seriously the road map looks more like taking the back roads of development. New shiny thing anyone? :P

I feel your pain I went through all this with X and Y curves for Gazelle cyclic input using a joystick I can only say building my own "Cyclic" made a huge difference for all the DCS helicopters. I did find for the Gazelle some saturation and because the cyclic input is centric in the Gazelle i.e. no cyclic offset for blowback etc* and also adding some curvature reduced the tendency for over correction and helped a lot. For collective using the tiny slider on my old Logitech 3D Pro with the combination of "Slider" and "Curvature" I could make the lower part of collective travel more controllable, great for pick up hovering and set down. This does then compress the top end of the transfer curve but that really wasn't an issue. For Anti-torque adding curvature can give the pedals more authority or broaden the centre travel depending which way you go positive or negative curvature. For me with the Combat Pros I had I liked having slightly more authority on the pedals especially for the Huey. But in hind sight the Combat pros where not so good but if it helps for the pedals your using then all good. :thumbup: I will say that with effectively a 250mm extension and moving the cyclic so it's down between my legs :D which allows me to support my wrist, really tames the Gazelle and the finer control input makes a real difference to the Gazelle and all the other helicopters too. * I am not a pilot IRL, I think this is more the way the control input is modelled and not the dreaded FM argument per se, just my observation of course. :)

Look new shiny,... :P

There is an indicator on the dash from memory also the torque indicator goes up about ~7% when autohover engages and drops back when disengaged easy visual cue. :thumbup: <edit> My bad the indicator is in the controls indicator with autohover engaged it shows white, just tried it, wow there is some drift in authover mode. But the torque indicater is a lot easier to glance at.

Funny you should ask this whilst there are real world restrictions on amount of wind and flying wind doesn't really effect DCS and the Gazelle to get into autohover in my experience. With high wind say 30 to 40K/h autohover the Gazelle will drift, something to be aware of. See my other post. BTW I had a brain fart on the NTTR map when making a mission and forgot the height of Nevada above MSL ended up with 100+K/H winds you can actually fly all the helis in DCS with that wind. Lets just say it was interesting. :D

Wind really isn't a problem, it really is a case of practise. If your using a joytstick with center detent this can make establishing a stable hover a little more tricky then it need be however again practise is key. And the window of setting autohover is fairly broad, really. As a side note I was flying Gazelle with a budy yesterday who was using just a Logitech 3DPro for cyclic, collective and anti-torque and he had no issues putting the Gazelle in to autohover so as frustrating as it may seem it really is a case of practice. :thumbup: My tip, practise hovering in the minigun version, as it has a better almost unrestricted view of the "world" which makes it easier to judge drift whilst hovering. Probably one of the first hovering skills people develop is to pick a reference point some 10 to 15 mtrs (30 to 45ft) out and hover trying to use that reference point to judge drift whilst hovering. Nice and it helps learning to hover initially. Practice hovering and visually selecting different reference points trees, rocks, parts of buildings etc whilst maintaining a stable hover. In other words train your brain to adapt to different reference points and not fixate on any of them and freely shift between them. After a some practise the only "reference" you'll need is the airframe and your "casual" view of the outside world. Then practise hovering looking down at your skids towards the ground or better still looking down at your skids towards the ground hovering over the corner of a building. :P Your training your brain to normalise your position or attitude relative to the world, you do it all the time when you walk or ride a bike or drive a car, why should flying a helicopter be any different? At some stage if your using a joystick you'll realise just how horrid that center detent and springs are for choppers. :music_whistling:

:D :thumbup: Beautiful man. ;)

Incoming,.. See I said be patient. :thumbup:

The DRM stuff keeps it's records on the Starforce server with "keys" on the you local drive. Good luck, I am getting used to reinstalling Windows once again, I had a break with Mac for a while and due to hardware costs and the general direction apple are going in I have come back to windows. :thumbup:

Are you referring to the Starforce DRM modules? If you use VR first change to non VR as the dialogue boxes end up behind the DCS screen and you can't see them. There is a process to go through unfortunately it has to be done in DCS. If your OS is trashed this might not be possible. :( For each module that has "DRM" click on the "DRM" for that module and a dialogue box appears, on that dialogue box is blue writing that says,.. "Activate or Deactivate Module" as a hyperliknk. Click on that and yet another dialogue box will pop up. On this one you are offered to either "Activate or Deactivate" when you click Deactivate DCS will attempt a deactivation transaction with the Starforce server. You need to follow this procedure for each DRM module. Log onto your ED account and confirm the status of your modules it should indicate that they are deactivated and will also tell you how many activation's have been used. Re-activating is also a long winded process. I find it helpful to have a browser window open and be logged onto your ED account so you can copy and paste the serial numbers in to the field during the activation process. For each module that is DRM protected click on the "DRM" for that module this brings up a dialogue box click look for the hypertext link "Activate of Deactivate" click on that and follow the prompt, copy your serial number for that module from the ED page and paste it into the field. Rinse and repeat for each DRM module! I was under the impression that you didn't need activation's on a server? Not sure. Maybe look at the new server version? Also be aware if you change or add HDD's or change the memory configuration or CPU whilst you have DRM-ed modules active that will accumulate points against an activation! This is not a good thing if you also use you computer as a test bed for testing hardware as you do not get any warning that it's happening. If your problem is outside of this raise a ticket and work through the problem with ED ASAP! Hopefully all modules will be bought across to the new user locked version of copy protection soon.

Nice video, I do think a lot of people get caught up in either trying to replicate someone else 's design or get lost but really it's got to be functional for the users application. That said it can be daunting if you don't know your positive from a crimp and why you might need a common return,.. :D I would recommend the use of at least suitable crimps for connection to the switches. Although for me soldering or crimping is fine. :) I've been rolling with a Leo Bodnar 836 which will provide up to 8 analogue axis inputs and 36 buttons or combinations of rotary encoders or two way switches. Actually I have no "bought" input devices for my VR sim pit but I do need to do a major rebuild going forward. :thumbup:

OKay but it's all I could find on it. Top secret squirrel stuff and those French pilots and all. :) :thumbup:

Have a look here from about 1:40 in start up procedure. Fuel pump on for 12 seconds. Starter to run spins turbine up to ~4000 rpm Then starter switch to up position until T4 temp reaches 400deg Then lets switch spring back to center "Run" position.

Which would be disappointing to say the least, it is the worst performing map in DCS and it was a full cost map that really hasn't had any love since we bought it. It's not like it's super complex compared to say PG it's not it's very repetitive so I don't understand way it's been left in the state that it has. Seriously I wish these things where fixed before other projects where considered, the map had like 5 minutes of MP glory before being put to the side because of poor performance issues especially in VR. If it was a test map why was it sold at regular price? As a side note It would also be nice if the PG map could be fixed before adding any more extensions, the PG map is only slightly better performance wise then the Normandy map in VR. Hopefully the opined VR improvements may help here.

Just keep in mind that physically anti-torque pedals work in a push pull fashion in that only one pedal can move forward and the other must move back proportionally unlike car pedals that allow both pedals to move forward independently at the same time. :)

Guys it's not that difficult and you don't need to be that fast or that high, just saying. For those that use a joystick you may need to carefully trim but meh who uses trim or a joystick?

I do think you have a point but unfortunately the "extras" are all part of "the package", I guess my point on VRAM capacity is that more VRAM usually means wider a bus which brings higher memory throughput. Besides being able to load more data into VRAM should at least help DCS overall. Interestingly the Radeon VII whilst not as good a performer in general with AAA titles even against the 2080 might and I do stress might be advantageous in DCS VR with 3840 vs 2944 shader units.