Hawkeye_UK

We already have easy air to air refuelling!! No probe damage (would be good if they actually snapped off etc along with next point) No tanker basket or boom damage No oscillation of the drogue pipe whipping back. No real sudden turbulence modelling or realistic weather effects re sudden changes. No line up procedure. Probe sometimes magic's into the basket from the side. No comm's (as in what you would normally expect with the tanker). Ability to put user curves in. Ok so that's why its easy - what i would say is practice practice and pracitice, its like riding a bike there is just a feel to it. Key is getting trim and speed right and making slow adjustments. I would state for air to air refuelling quality of hardware does matter quite a bit also re input.

Push insert to switch to 3rd person view of vehicle, can then use CA. It is ludicrous though that something such as view binding cannot be sorted with just the reverse of the axis - i mean how hard can it be seriously. Always amazed me ED's inability to sort out simple problems and easy wins. Absolute shambles given VR is the future but already well adopted by the community in the present.

This is a Pointless post wthout specs you do yourself no favour. The whole point of the forum is to try and find help and compare with people with similar specs so as to gain insight / assistance. You didnt even mention how Supercarrier was running in 2.5.5 (which it clearly can't btw) so your comparing completely separate modules. As i said a pointless post - hopefully ED will close it.

Didn't say in the grove that's common sense unless sudden wind direction changes /gusts - he's using alot during the turn obviously. Also not referencing the ball flying, was referring to how the jet is bleeding speed compared to some of the first comments in the chain.

Lol why has no-one referenced that for a start its a different airframe lol. Why you guys thus trying to replicate it or reference the differences to a Hornet C. Bigger wing surface area for a start (90 square feet circa 25%), different engines(extra 9000lbs thrust), extra 10,000 lbs of weight. Break turn has very high g in the break, loosing speed much quicker than a bow break "normal circuit" with less g and smaller wing/mass. Don't see what the commotion is, trained and experienced pilot flying and simply that doing his job and a bit of showboating. As for using the stick alot, again ?? He's getting nose authority, also he's using alot of rudder to get his aspect to where it needs to be.

And your PC Specs are...... You managed to use the Supper Carrier as a comparison in 2.5.5 how....... ;-) You where on which map..... Your settings in DCS are.....

i Know FLIR has 2 modes, so either the sky is painfully bright while the ground is ok, or vice versa - both are blinding. NVG is a separate issue - and not listed in my post. Love to know how you use the NVG whilst still using the TPOD or EHSD, or any MFD. I have gamma set to 1.1 also night or day. Your the first person i've come across who think's its acceptable. Do you fly competitive pvp Multiplayer with players controlling the ground units and shooting at you, aka not flying against AI. Makes all the difference as no time to mess around re locate unit, swtich NVG off, use sensor etc, ingress back to target. Need first pass strike abilities and bug out.

Happening in MP - not so much a Razbam issue but ED and already reported. Happening on choppers also.

Lol thats funny and your right, was late at night lol - it's ridiculous the community manger just states ask Zeus and pm him directly if any questions. Point is - Razbam do need to start listening 2 years down the road over vital and basic issues if they want people to support them, aka us, going forward. Frustrating when coding being done on things actually that could wait. Get whats already out there functional.

@Razbam, Appreciate your having issues with coder's however @Zues please can you now sort this yourself. Despite numerous posts over the last 3 months by myself and numerous people we still are no further forward with HUD and FLIR. Have you tried flying your own module yourselves in VR at night, or do you not because of the reality that they are unusable - it is literally blinding and i would suggest potentially dangerous if your on a night mission and HUD flir is activated, it actually really hurts your eyes!!! Isn't it time you started putting a disclaimer on your product that this module is not VR suitable for use of some of the features at night re can physically cause eye pain, and that equally for all users the night attack harrier is now not usable at night. I will ask again - please @zues can we have MFD buttons that brightness clicks up and down (not a slider that was hinted at in special that cannot be adjusted in flight), rotary dials to control HUD video brightness implemented and a HUD FLIR that doesn't blind you. 3 months since 2.5.6 - It's time to sort if you want long standing members of DCS to continue supporting you. New updates in yesterdays patch that involved coding for the harrier in the latest patch not exactly the most vital - again i will state get the basics working first.

Possibly commercial is about the only one i can think of re Viper release at similar times given how feature complete and stable the JF17 is. As i said doesn't affect me as only use the OB but feel sorry for those who only play on stable architecture. Should release exact same stable version just with JF17

Another Update - Nothing done to Night HUD FLIR - Its actually dangerous i would suggest for VR users - it is utterly blinding. @Zeus - Enough is enough, coders's or not please can you persoally sort. This is more important that SEAM mode released today or anything else, its actually makes the whole system unusable at night.

Alot to render on the island - that aside and with respect do not expect to run the latest software with older hardware. Its brutal i know and not meant to offend its just the reality of the situation. With a 2080+ its playable.

Agreed , my patience with Razbam has dried up this year, especially since 2.5.6. MFD brightness buttons awaiting since day 1 of release still to be completed - absolute joke, all the time working on South Atlantic, Mig 23, F15E and according to an artwork release a EE Lightning. Meanwhile..... EHSD can no longer read at night / low light Hud Flir way over powdered can no longer use it at night. TDC slew axis, the only plane that it sticks in (reported since release). Basic stuff and vital, although here we are 3 months later and still awaiting adjustment, although in fairness its been 2 years since release and this should have been day 1 items. Intern level coding also. Agreed Deka are an example of how to knock out bugs, just look at the OB updates since they released. Impressive. Whatever their next module is i will buy just to support them. As for Raxbam why oh why are they doing the F15, it should be Heatblur or Deka. Razbam PR / Bug fixing = Joke currently. Even their community manager told me to PM Zues directly if i have any questions.

A10 is not restricted in anyway - you need to read the manual on how to operate DCS and the A10. Custom payloads are setup in Mission Editor and then available for MP, SP loadouts etc. If you put a "!" at the start of the name it will appear at the top, handy when rushing to get airborne in MP and you dont have time to trawl through all loadouts.

Maybe pass back the feedback that the Slider is a very poor concept/solution and that the community is hostile as such. A slider would not allow to fly the harrier with changing light levels (that is unless we are meant to fly it middle of the day only). Seriously the MFD brightness buttons need to actually work. Notice in the picture Zues posted there is no EHSD map showing, which is a concern as this is what is part of the problem as the map looks washed out and cannot be read. HUD night flir no reference. Can you confirm that as community manager this has been passed on? As for PM a dev if we have questions, isn't that the whole concept of a community manager to liaise to actually allow the dev team to get on with their work, as in your role @Decoy. Thanks

Already been announced indeed they showed some artwork of this very thing.

Because its no doubt easier. Hence why i raised it re MFD buttons not a slider you'd think after 2 years they would have the MFD brightness coded, you know being a basic requirement to use the actual jet. The EHSD is totally screwed at night now also and low light cannot be used re map, was one of the best in DCS now the worst. As for the FLIR on Hud - well that is blinding in VR and totally unusable. But to even mention a slider just show's how out of touch they are - question do you actually fly your own modules anymore in a competitive multiplayer environment in all weather / times of day - clearly not. Unfortunately my patience has run out with Razbam this year with pathetic time frame's for a response or just ignoring completely. They are way behind other dev teams in terms of customer feedback and communication, it actually feel's like the Razbam forum is pointless - my only wish is that Deka / Heatblur had been given the F15. Cannot buy into any more Razbam products until they sort out there customer relationship and show a willingness to sort out basic but vital issues. Stop working on pilot bodies, Mig 23 and Falklands and get the Harrier basic's use sorted. Eye candy and other functionality can wait. A night attack harrier that cannot be used at night just about say's it all really. Poor performance from Razbam has to be said which is a shame as the Harrier has the potential to be one of the best modules.

also how about actually making the MFD buttons work for this, so in mission as the light levels change, not in special, thats pointless when already flying. Have raised a whole issue about this and the FLIR in bug section 3 days after 2.5.6 came out. You will note there was a similar issue with the JF17, corrected on the next patch. Whilst were talking about issues and someone from Razbam has actually responded any news on the 2 year wait for the TDC slew to work properly re axis binds?

When ?

I'd love to see the justification for the JF17 not being in stable when the Viper went into Stable mid November 2019. There really was no argument for not doing so prior to 2.5.6 coming out. Agree with the OP. So keep a module that is stable and nearly finished in OB yet release a very early access Viper into Stable. Ignoring all the weapons system to be implemented we can't even add waypoints yet in the Viper so there is alot of potential stability issues still to work through! If only ED were as thorough as Deka in their product releases, or on fixing bugs and improvements on new modules in the same timeframe. Just have a look at the JF17 change logs, puts all ED modules to shame to be fair in terms of workflow. Surely it was a commercial decision and nothing else, aka two planes coming out at similar times. Doesn't affect me personally as i only fly OB but feel sorry for those that are awaiting the JF17 yet do not want to put up with the OB architecture. It needs to go to stable, as in release the exact same stable version just with the JF17.

A very constructive point to be fair - also made me laugh lol just the effort of taking the screenshots - brilliant. All the time the Supercarrier, just eats the dev's resources and we see little progress on Hornet / Viper. To be fair the Viper should have been ED's crowning moment to pull in may customers from BMS / Falcon 4, instead it was rushed out and launched way to early with not nearly enough EA progress made in the last what 8 months. When you look at it compared to the Deka module and how functional that is, wow. Say's something when third party dev's are knocking out modules of this quality, Heatblur also. The thing that has amazed me with the JF17 is Deka's willingness and ability to quickly resolved bugs etc, just look at the patch notes for Deka compared to ANY ED module in the last 7 months.

They are adjustable, i'd be more concerned with FLIR and especially concerning JTAC laser and assocaited smoke, cannot see anything anymore as the smoke acts as a heat source!! Night operation of FLIR with JTACS is now impossible, have been for 3 months, to be honest fed up of highlighted it to ED and patch after patch nothing done. Aircraft affected - F18 | F16 | Harrier | JF17 | A10C

Been this way for the last 3 months since 2.5.6 - Its a real issue have highlighted across numerous posts. You would think FLIR would be a priority even over A2G radar - ridiculous really especially with JTAC smoke & laser you cannot see any of the targets. So absolutely ruined use of JTACS at night, which in turn ruins alot of very good campaigns such as A10C Operation Piercing Fury and as for multiplayer, it has ruined night op's on our server. Worse is the ground and aircraft night lighting if a moon is present, ground vehicles glisten from 15 miles away, so obvious and get picked off by CAS, fed up of reporting it to be honest to ED and nothing being done.

PS - i should have stated though DCS in VR is a whole new game, its just amazing to be honest the immersion is fantastic. There is no going back to 2D ever.