Arctander

I think it’s fair to revert to ‘generally understood’ as a point of reference where ‘adding’ something is seen by 99.9999% of people as ‘putting something in that wasn’t there before’ - I.e. ‘new’

I thought the Viper was a few months early, with the hornet devs being moved into it and the lack of progress in 6 weeks it is becoming clear it was 6 months early, at least!

LMFAO when I worked it out.... mig28.... glorious.

I can agree not every bug fixed is added to a change log, but any ADDITION bloody well should be, or the customer is unaware. Is ED’s change control really that absent, and you are really ‘ok’ with being kept in the dark about changes?!

One word. Viper.

There is, indeed, nothing new for the 16 or 18. A few bugs fixed, nothing ‘added’.

You mean the one just posted? I’ve edited into my previous post the text for clarity. https://forums.eagle.ru/showpost.php?p=4099862&postcount=76

Default DCS 2.5.5.39003 Open Beta DCS World Serverlist refresh will not infinite looping when user pressed F5 too often. AIM-7. Fixed bug that caused the missile seeker to not see chaffs. DCS F-16C Viper Fixed crash with rockets firing after selective jettison F/A-18C Hornet Fixed DCS hangs on SA page. DCS C-101 by AvioDev Fixed engine sound that was broken in the latest update (real engine sound still WIP). Fixed startup training mission. "VOR ON" step after startup will not pass without moving the NAV Volume selector in VOR-ILS-MB equipment. Gear up and gear down commands added. Gear emergency extension works now when using input command. AoA indicator does not jump anymore from max to min and vice-versa when turning the knob with keyboard or joystick button. Control stick can now be hidden using keyboard or joystick commands, not only click-spot. Ventilación Emergencia / Emergency Ventilation" depressurizes now cockpit". Gear override button (crash button) has now a press and release function. Welp. That’s not really a step forwards. I hope a lot of work has been done behind the scenes on the Hornet (and Viper) and a much bigger one will come next week.

Yes - you do, but that's not the blocker. The Blocker is finding the funds to; a) Buy Bing Mapping data. b) Use Azure AI to map and allocate features to terrain types c) Convert the result into a mesh and texture with objects that could be used in the DCS engine. This is an incredibly simplified set of steps and is only possible as MS are using it as a case study in how to use Azure AI as a selling point for industry - so they are throwing HUGE money at it... something ED just can't do. So forget it. (Sadly)

Great post.

If you’re asking can ED replicate MSFs2020 tech - that’s a big fat no. Msfs2020 iirc is a completely new engine which enables this tech. For Ed to do similar would be prohibitively expensive, reduce their income stream, and frankly not worth it.

+1

Agreed. I have on my wh throttle comm four way, Back - teamspeak Forwards - comm 1 Down - comm 2 Up - comms menu I use ‘up’ solely to close that menu after using my radios....

As others have stated - there are issues getting hold of the documentation, without the Russian governments ok. Razbam are to work on the mig 23 once the Harrier and Mirage are completed. Also - I think ED have more than enough on their plate that adding on top of it. Let them finish what they already have in the pipeline, and once they have capacity to add more, then let's talk about what that is.

How many of those ten are complete may I ask? Because therein lies the problem.

1) I'm sure there were too - but I don't have to like the fact that it has undeniably impacted Hornet development when we were told previously it wouldn't, and it's a state of affairs that has now lasted for at least two months (that we were told about) 2) Nobody promised me it would be the sole focus of ED - and that's not what I expected. What I expected was that they managed projects so that the 'first' product to launch would normally be the one on which new systems/capabilities would be enabled first. At this time, we still haven't been told if the Hornet systems/avionics devs have moved back onto it - which is clear that they haven't as only (mostly niche) weaponry is being updated. I also don't have to like the way many of the functionalities on the Hornet are incomplete like the AZ/EL page etc. 3) Quite how you can say the hornet 'helped accelerate Viper development' when the Viper has an INS enabled, a SAM mode and will get TWS first, along with the TGP (or at least markpoint) HUD designation. This shows that the rule at the moment is that the Viper gets first crack of the whip, and it's fair to say that as the Viper is the 'poster child' for many - who is to say that that state of affairs will be unwound? Can we expect the Viper to get everything first now? Just look at the latest Newsletter.. while the Hornet TWS is mentioned, it is after a LONG line of completing weapons, and introducing new ones, which infers that there is NO ONE working on the Hornet Avionics/Radar and is not expected to be for some time... There may be very good reasons for this from a development stand point, but ED aren't saying that. What they are saying is 'one benefits the other' but in that case why not complete a Hornet system and then port the equivelant new systems onto the Viper? Again - no one promised me exclusive development of the Hornet, but it would be fair to expect first deployed, first completed, and right now it feels anything but that, so I absolutely don't have to like the treatment the Hornet has got as a result of the Viper being released far too early. And so, yes - I do feel betrayed. Not because anyone 'promised' me anything - but because I had an expectation that ED would complete the Hornet in a reasonable time frame - and that patience is wearing extremely thin. In addition I have an expectation of 'fair' - and while a temporary reallocation of resources to help get the Viper out of the door is acceptable, the length of time it is turning into and the poor messaging around this space deepens that feeling. You may disagree with me (obviously you do) - but I am not alone in this feeling, and if ED continues down the path of needing to push out ever more bare bones modules to keep the lights on, then more and more will start feeling this way. What if the Viper gets pushed to the wayside for the Hind? Or the Mosquito? Or the F4 that this forum clamours for? Or a Pave Hawk - or anything else? ED (and this community) have to face into the fact that there is a problem with this business model - and we shouldn't be begging ED for 'more' modules - we should be begging them to finish what they've started, and fix the core issues of the sim (poor ATC, unsynced clouds, poor missile flight/guidance model, poor spotting, poor ai, poor damage model etc etc). If their business model needs to change to enable that, so be it.

Agreed - I use the SA page for that purpose - but even then I find the performance of the radar even with the scan elevation correctly set very lacklustre. There's also it seems a gap between BVR and the ACM modes becoming useful...

^ this. Very good point and a pain point for me too

This was the only point tempting me... that canopy in Vr. But after their treatment of the Hornet I decided to be strong and not buy it. Very glad I didn’t know seeing how half baked it was, and the impact it’s had on my Hornet.

And this is why Many Hornet pilots (especially those who don’t have the Viper) feel betrayed.

Imo the priority for the next patch is TWS. For the Hornet. And a TGP market. Az/el Alignment Other non implemented avionics. But hey. We don’t always (ever) get what we want.

Yet another example of ‘half done’ logic from Ed. Don’t expect it to change until the Viper has been very much improved.

I completely agree. Ed’s practice of dropping something when it’s half implemented to work on something else leaves nothing but frustration. Sadly, I wouldn’t expect it anytime soon as every man and his dog (except the weapons guy) is on the Viper, so don’t expect any systems work for the foreseeable (something to be clear that I am very much angered by) - and even once they come back they still need to sort out TWS... it’s absolutely bananas that the Viper will have a better A2A capability and better targeting pod before the Hornet when it came out a year and a half afterwards. If ED hasn’t learned from the reaction to this debacle then I fear for their organisational priorities and sustainability.

That’s what they’re asking for surely?

I also have seen this. It’s pretty clear to me that this behaviour started after the Viper dropped as before if it couldn’t get a lock on a target on the radar (most likely as a donor track and the radar elevation was off) the lock would just fail. Now - it jumps to whatever is next along that bearing... and when that happens to be the enemy awacs 80nm away when in a 20nm fight in MP it feels bad, m’kay.