VampireNZ

I think the biggest advantage of this would be not having to see the weird 'wobble' of the blades as they go past - all following different paths and just looking super-strange! You can also see the angle of each blade changing rapidly as well as it goes past - interesting aerodynamics indeed! If you had tracking that bad on a RL helicopter it would last all of 10 seconds before exploding. You should be able to look at the rotor disc and see just that - a disc of blades all following the same path. Yes obviously this disc 'moves' to provide thrust in required direction/flap to equality etc etc....but they all still 'track' the same past a point! Have carried out a lot of ground and in-flight blade tracking on various choppers. Interestingly this makes tracking 5-bladed MD500's (and other 4+ bladed choppers) a lot harder than the 4-bladed as a blade can drop into the wake of the blade in front of it and show as tracking while on ground/hovering, however when you sharply manoeuvre it will drop the 'tow' and then stick out like a sore thumb doing it's own thing....like the DCS Hind with all blades at all times lol.

I may be mistaken - but I believe ED implemented that behaviour with the trim hat as you describe - the longer you hold it the greater the input, so not a linear trim rate. But yes the main issue is that one 'bump' of the hat in the lateral direction doesn't account for the inertia of the system as you describe and immediately inputs a large dose of aileron trim....too much 99% of the time. Pitch trim is fine, but personally I never use pitch trim in the Viper....maybe a couple bumps nose up on landing if I am doing a long boring precision approach or something.

It would be nice to ditch those 68kg depleted uranium tubes and fit some 10kg aluminium ones . A few more kilos fuel would be really nice.

Lol he isn't trolling you - if you keep flying the pre-inserted 'map slide' will swap to another section of map adjacent to the previous one to continue tracking your progress. Now this may be a really bad section of map and you might be shown in the lower left corner or something silly - but it should swap. Although saying that I have had the situation where I have got to the edge of the actual paper map installed (so you can see the white edge of the map with distance marks/writing etc) and no new map was dropped into the display - the plastic tracking cross just stayed at the edge of the display. Maybe that is what you have encountered? In any case the whole map tracking system is obviously WIP so I wouldn't get to hung up about it just yet. I just use it as a novelty really, as the actually doppler navigation system is really good (lots of use from Mi-8 flying), and combined with NDB's gets me where I need to go.

Just going from memory here - but I think there are several different keybind options for firing weapons (think Weapon Release is one - or something like that) - but only one actually works. Try binding trigger to a few of the other options and see how you go.

All good man - I am not trying to start an argument here. As I said these are just views from an actual SME with 1,600 hours over 6 years on an airframe, that worked with a simulation team in developing a full motion FAA Level 2 FTD training sim (including every single malfunction possible to every aircraft system - so yea I was never perfect lol, but I did know what colour the displays were). There are also actual SME's, and self-proclaimed SME's....there can be a difference. Bottom line yes you are correct - hence BN's response - 'we would need more specific information to change our current modelling'. You got it, they will listen, simple really.

Interesting - I don't think BN's reply sounded like "We don't know' at all. I get the impression it is more "The HSD display is currently modelled as per what we consider as reliable information for the version we are portraying - if you have 2,000 hours flying this specific model F-16 and are used to seeing red HSD rings, or are looking at the exact same model avionics systems/operating manual showing red rings, we would like to know and will refer the info to our own SME for consideration." - maybe it's just me . Not saying it is impossible - but the MFD displays changed all over the shop with different blocks/upgrades/versions etc.

Guys to play devils advocate, this is a pretty simple functionality that any operator of the aircraft of the appropriate avionics generation would be fully aware of. As ED have access to SME's that have operated this aircraft block I would err on the side of saying they are probably happy with this current system depiction, unless as Bignewy says there is any clear evidence to the contrary. (agreeing with ED - I know crazy right lol). I have seen plenty of Vipers will all sorts of variations in MFD colour schemes etc. so it is nice ED are sticking to one particular avionics gen so closely. As per Rule 1.16 (which I am quite familiar with lol) ED/we can't post any 'specific' information about the appropriate Viper systems, but ED don't need to if they have a dude that flew it saying 'yep that's how it works' - which is more than adequate. Just thoughts from a guy who worked with the development of an Air Force simulator as the aircraft systems SME and advised on the correct system interaction/functionality etc - when something wasn't right, the programmers I was working with didn't say 'prove it' they said 'thank you, so how does it really work?' lol. So trust that ED have the right SME's on the job that say 'system A works like this', or 'This needs changing'.

Hmm that is good to know. This is something that might need a look at and sensitivity toned down a bit. It is possible to align an aircraft in windy conditions with it 'moving' around on it's oleos. You only have an issue if the aircraft actually changes position/location during the process.

Done

Nah just jokes - looking fwd to the Viper getting some more attention leading to an increase in it's functionality and capabilities.

Yes there are - several IIRC. Can't remember which one I use - the one that just increases font size, not the colour as well. Use a Reverb G2 and can read all MFD font fine with PD 1.0 & 70% steam SS. (100% SS you will be gold). EDIT: I use this one - https://www.digitalcombatsimulator.com/en/files/3309263/

Not that pilots listen....

No not in a 'Dive' - yes you can use it fast and low. Just remember the Hind is 'relatively' flat even when fast (which is why you need so much back stick when lifting off, can have cyclic central flying at 250 kmh etc.). The difference between getting what you have in your pic, and a solid CCIP gun solution is only a few degrees more pitch, which is easy to accomplish when you recognise what is happening. If that requires a little bit of loss in altitude then just start gun run a little higher - but you don't need to dive-bomb your target.

2.) Yea I was wondering that too - I know ED have programmed in a 'delay' for Petro responses to mimic a RL person, but been watching Casmo fly the Hind with a RL gunner up front who opens the sight on turn-on and immediately goes to work finding targets etc. The huge wait for Petro to get his A into G is painful as you are flying in towards the AAA waiting for captain slow up front to sort his shite out lol.

You are flying too slow/flat. If you pitch the nose down you will see the CCIP pipper come 'alive' and move up to match where the bullets are actually impacting. Was doing the same thing when I started flying the Hind. Can obviously be a problem if you are shooting onto 'rising' terrain so have the nose up etc, and it will also not be able to calculate impact point as accurately, but remember the onboard computer is just calculating the edges of a triangle, so if you don't have an adequate 'triangle' it just says nah. As you are so 'flat' it also sees the impact point as 'out of range' hence no yellow light on opposite side of unit to green light illuminated, and see how the thin range line of the gun pipper is still way round past 3'oclock - it needs to reduce to the start of the 'fat' section to be at max range (and yellow light comes on) - and where this 'fat' section ends is min range. You also need to step on your right TR pedal a bit as well - see that little triangle at the top of the gun pipper off to the right a bit - this is your sideslip indicator. Give it a little right pedal and this will come back to the 12 o'clock position. Is a really nice feature of the sight. As stated above the CCIP pipper can be super accurate

Looks like you have sussed it out - I had the same CPU with a 1080ti and Reverb G2 and it couldn't hack it at all. You would be doing yourself a LOT of favours getting a 5900X CPU to go with that GPU as the core power is substantially better than Intel options (5950 not worth it for a few extra cores - 5800 overheats badly). I upgraded to a 5900X & 6800XT and saw a nice improvement in DCS (but not great - all other VR games are amazing now thou) - but more importantly the CPU generally sits around 5-6 ms, maybe up to 10 if on heavy maps. You don't want your CPU anywhere near 22ms as it has no way to 'handle' the shortfall - unlike the GPU that can drop frames etc. So I ended up adding in some shadows to the cockpit (with the 'shadow range' mod to limit to immediate area of cockpit)for a little 'eye candy' after all these years of potato graphics lol. Some of the code in DCS is so suspect and dodgy thou - I remember when testing out settings with new setup there was a IA mission on Nevada with some warbird flying around in the distance - frame times were absolutely in the toilet if that dot was on the screen at all, even if it was 20 miles away! Was good frame times...look at warbird speck....performance of sim cut in half! lol. Also just FYI, 4 sticks of RAM work better than two with those CPU's as well.

I don't think pitch trim is the problem when you are trying to trim your jet to fly in a straight line with a pod attached/ after dropping a weapon etc. But yes as per above, I have mapped a rotary encoder to the trim wheel on the trim panel for lateral trim, helps a lot. Quick stab of the trim hat after weapon away, fine tune it later with the wheel.

Yes, a little annoying - just another EA 'foible' to work around at the moment. Just imagine how nice the 'sorted' Hind will be to fly lol.

Nothing - the trimmer system at the moment is bugged and inputs additional cyclic after you have hit the trimmer button. Major PITA in this type of heli that relies on constant trimming, but that is what we have got at the moment unfortunately. You just need to work around it. Always happens badly while I am slowing down - set a nice nose-up attitude descending at around 3m/s on approach and hit trimmer button to get stick out of my guts....nose jumps up another 5-10 degrees . So then jam the nose fwd and hit it again. Trying to 'anticipate' by releasing the stick a little then trimming, knowing it will jump back to 'kinda' where it was. But yea much like the Hip, the Hind requires a little planning if you want to do a smooth 'controlled' approach. You will find the Hind takes a while to slow from high speed, but once you start getting down to <150 kmh with the gear out it will slow down faster at the same pitch angle for that final landing settle. Just always be feeding in a little collective as you get below 100 along with right pedal, and as you approach 50 you will need a bunch of power and pedal to avoid VRS - don't wait for the vertical speed to start racing away, anticipate the loss of lift with collective, especially as you go through ETL. But with rolling landing into wind you may not even go through ETL and will have a nice easy let-down at 50ish kmh.

Yep I get this 'rocking horse' effect also when trying to fly around 150kmh S&L. Was just doing the Deployment re-worked campaign and flying in formation with the other two Hinds on Mission 3 and as you are flying slow with small variations in pitch, the 'Stabilization System' starts rocking the nose up and down (shown by the trim indicator in the Pitch channel cycling up and down) - it is actually quite nauseating! Just solved by disabling the pitch channel and the rocking stops immediately. Trying to 'trim' out the channel using the trimmer button has mixed results due to the trim overrun situation, but even then after cancelling out the deflection, it will start rocking again in around 5-10 seconds. Increasing speed to 250+ish and it doesn't exhibit this 'rocking' behavior and you can hold a steady pitch. I use a VKB full length floor mounted stick and minimal curves - have no issues holding the Hip steady in slow formation with Hueys etc. Based on the SAS behavior and the trim overrun issues at the moment it is pretty clear ED have mixed up a few ones and zeroes in the code for the Hind SAS system, as the Hip has a similar system and doesn't have any of these issues. Fingers crossed they get it sorted!

Has fan installed - looks operational to me!

TBH you would do yourself a lot of favours trying to lock stuff with your radar if you just disabled Link 16 info once you have ascertained where the contacts are - (displayed lower left of FCR page). You can map the Datalink display option to your throttle (as per RL jet), and clear out the DL symbols to more clearly see when your radar has an actual return you can lock. Yes you get diff symbols as described above, but you don't need the link 16 info once you know where they are anyway - your main priority is getting a solid native radar lock to employ weapons.

Great mod - thanks! It is a shame all HUD projected imagery in DCS looks like it is on a perfect LCD screen, not a projected image.

I use Kensington Trackball stuck next to my throttle - works perfectly in VR, and you can map some generic inputs to the extra 2 buttons on it (and combinations) - so I have ESC and F1 mapped, along with combined-press of top two for spacebar. Also it becomes very natural to reach out and use button boxes positioned in front of you, along with Cougar MFD's and I also have a full-size ICP mounted in front of me for F-16 - no problems locating the buttons with some prompts stuck to a few buttons etc.