VampireNZ

I found the best mod just went for the brute-strength just make it bigger approach, works well in VR at least. Text still looks like crap but at least you can read the curser/contact altitudes etc. https://www.digitalcombatsimulator.com/en/files/3309263/

Maybe they should 'fiddle' with it till it doesn't looking completely f'ing stupid...

Awesome looking skins, thanks! Edit - noticed it was limited to Israeli Vipers, makes sense :)

Stay under 150kph and don't try to 'correct' the swings as such - but when a heavy load swings out sideway it will tilt the helicopter, use gentle cyclic input to bring helicopter atitude back to level during the swing, and evenly release cyclic force as the tilting force levels out. The load will cease its current 'swing' somewhat. Very easy to get it hanging under the heli stable again...till the next swing sequence starts up. Bigger loads such as logs will also be subject to the sidewinds much more than barrels etc.

Just another little bug in Mission 9. Approaching the Sub-Base at the end of the mission and the pilot makes his 1hr operations radio call to ATC again.

See you in 2022 then....

Using that penal colonies flag to represent New Zealand.....

'Fixed Jester TWS-A /TWS-M endless loop with phoenix in air and player commands during TWS-A' Says who exactly? :smilewink:

Totally agree, the doppler nav system combined with drift info, and throwing in some NDBs if required, is awesome for cross-country nav. I fly in VR and just peer over at the co-pilot panel and zoom in to see my deviation if any. Would be pretty awesome if he gave you a heads-up maybe if you reached 1km adrift from track for example. Pretty much turns any crosscountry leg into a VOR/DME beacon nav solution (flying the outbound 'radial' for set distance from diss enable posit).

Happy to d/l the SC module and keep my current Mi-24 Wallpaper :thumbup:

F/A-18 spuds into carrier deck at 208kts and 5,000ft/min rate of descent, 100% A-OK. Mi-8 takes one 7.62mm round to the tail - tailboom falls off and chopper crashes and burns. Legit DCS. :huh:

ED please watch Apache Warrior on Netflix (yes I noticed it was an Apache not a Hip) to see how resilient a heli is in general to small arms fire - I am getting a little tired with LDG Gear/Tailboom etc. falling off after a few rounds from an AK. Wanna fail engines/systems with an AK round through the engine/electrical bay - fine, but tail falling off - really? Also - for the love of all things Stalin, please make the Mi-24 a tank like it actually is in real life!

Generally the majority of heli rotor noise is the TR blade tips breaking the sound barrier. A good example is the MD500 TR mod that replaces the twin bladed TR with a 4 blader that runs slower - so a lot quieter.

+100 Or at the very least could we get a binding option enabling mapping to a controller for the ball call? I am not looking fwd to fumbling around with my trackball looking up to my right selecting comms menus in VR while in the groove lol.

Yep, and instead of adding my experience with the bug to each of those threads, I listed it here. Maybe one of these threads might get a respponse :thumbup:

I am not sure where this reasoning is coming from that any issues with Jester are due to the user having only a 'few flights' or having just bought the module? I have many hours in the Tomcat, and Jester still behaves the same way as after the first few flights. Also no one is is saying he is 'useless' or 'complaining' - they are bringing fairly serious gameplay-influencing deficiencies with a product to the developers attention. Personally I was saying that that a few issues with the Jester component of the aircraft is taking away from an otherwise incredibly good module in DCS. Heatblur are well aware of this and don't need you jumping to their defence with patronising comments that assume everyone only has a few flights or are 'new' to the Tomcat. With 100+ hours I am well aware of the 'workflow' in the Tomcat. I am also aware of other pilots with more than a 'few flights' that have stopped flying the Tomcat due to Jester. Jester is still being developed, and we can only hope he improves with age.

With the SC around the corner I decided to dust off the Tomcat again and venture into a MP session - went as expected, not well :(. After launching 4 Phoenix and downing 3 targets using the default Jester radar mode and letting him do his thing, I started to direct Jester to STT a single target ahead for the attention of one of my Fox 1's. Somewhere during this process a constant rapid 'clicking' sound began repeating from the back seat which seemed to me that Jester was hammering away in a constant loop on some cockpit button. The radar subsequently was unable to remain locked on a target and would instantly unlock again. This occured if Jester STT'd a target, or as the contact got closer I tried all the VSL and PLM/PAL modes and same deal - instant unlock. As such I was unable to launch a Sparrow and had to turn in on the bandits six, get Fox 2 tone and launched that way. The constant clicking continued and I was unable to get Jester out of it by putting him to 'sleep' using the menu option, and I couldn't move to his cockpit to 'reset' him as I was in MP. The instant unlock behaviour continued as I closed on a H2H with more contacts - with the radar STT'ing to the target and then instantly unlocking again (also indicated by the TCS flicking to the target then 'resetting'). Once again I had to close to Fox 2 distance - at which point DCS froze for us all on the server and we all rage quit. I didn't get the trackfile. Sorry this may not be super-helpful in tracking down the issue. I am also not a 'new' flyer of the Tomcat (which seems to be the new 'reason' for Jester playing up) , and have more than a few flights with 100+ hours and 200+ landings - I have a fair clue how it 'should' work.

This - the 'Jester Experience' is really letting down an otherwise awesome module. :( I realise the whole AI crew member is new ground and is clearly throwing up some significant programming difficulties - but there are still the same issues that have been around for many moths like simple IFF, and basic common sense in radar usage. Not salty, just a shame really - I am just hoping when the SC is actually usable and working properly in say 6-8 months(standard ED period to iron out bugs on new EA releases), the Tomcat will be more user friendly also.

https://www.digitalcombatsimulator.com/en/files/2802853/ Just use the version that removes the AP display. Obviously this should be an option in the aircraft Special tab in the options, but we all know by now ED couldn't give a monkeys about the customer experience, and we have to solve these simple problems by way of modifications by other users.

Check your weight in the re-arm screen, is easy to overload the chopper with a full load of fuel and weapons.

So given it was an honest mistake and no ill was meant, those that paid more for the same pre-purchase of the product for absolutely no reason before it has been released will be getting an appropriate store credit. Thanks! That is really big of you ED, I am sure your loyal customers who pre-purchase products to show their support will appreciate the kind gesture in these dark difficult times. :thumbup:

I assume a partial refund is coming to all the early pre-release purchasers who tried to support ED, only to then sell it with 50% discount right before release...? It's not even like we have been able to use it in the meantime so actually gained any benefit whatsoever, so very different to a module going on sale later after release. ED are really going all-out to try and dissuade pre-purchase decisions lately..

I got to this bit and thought yea this must be a joke...'I am quite surprised the Huey, an obscure chopper I have never heard of outside the sim' But in reality there is a whole generation now that probably has no idea what the Vietnam war even was.

Also was just flying around landing at every 'clearing' beside the forest on the N side - just quit the mission in the end. No directions of guidance to help find the right 'spot'. Edit: Just checked the mission in the ME - if you mean the place we need to go is the collection of items to the W of Apsheronsk, that is 16km away, no way would I think of flying that far looking for an oil oil rig that could be anywhere. Some clearer instructions needed, like fly 15 km NW lol. Is a shame as am really enjoying the campaign.

Not in flight aside from mentally adding everything up (ZFW, current fuel, stores), on ground just open the rearm screen. Generally at landing you will have no stores remaining and min fuel so pretty easy to determine per Steph21's post above, but honestly just place the FMP at the top of the staple - which is in the middle of the 5 deg lines placed on the landing spot. The Viper is crazy easy to land.