falcon_120

I sense that ED is increasingly giving more and more importance to user feedback to steer their decission making, which is nice. Given that approach, i really think they should send a poll (simple one) when you buy a module to describe your motivation for it, that way they will have data to understand what the community actually thinks when buying something, it could be: -I really like the module -I just want to support you but dont do this shit again or I quit :p -More options

I just wanted to say. I'm an open minded customer who loves DCS too much so I would like to know, if ever happens, if ED is not financially profitable, if they think of a new revenue model to make it profitable. What I dont want is to wake up one day to read a post saying "Dear customers we've gone bankrupt... farewell". I would love some notice before so actions can be taken.

As mentioned before the topic is broader and maybe you are missing the point on purpose. Should the hornet radar performance be decreased? Most probably. Is the viper radar overperforming?, i'm seeing this to be also the case. Along with all this, some people here are saying they cannot detect things until 30 nm, i can tell you after many hours flying both hornet and viper in dcs that they are encountering a bug or not managing the radar properly. In my case, in any MP server i jump in, i'm able to see contacts at more than 80 nm even 120nm, around 60/65nm for fighters, i think we can agree this needs to be looked at and tune with SME advice ofc. Hornet and vipers are now behaving like eagles and tomcats, there is really little tactical value to fly an f15c now for bvr given the situation. Maybe when ED launches the F15C it will see fighters at 150 nm XD who knows. Enviado desde mi SM-G950F mediante Tapatalk

Well, not sure what to say, but the "other day" is very random. It could be caused by many things (improper elevation management, beaming...). Test a simple mission with a mig29 head on and I can tell you you will detect it much before 30 nm (I dont know the exact figures though need to test it) 99% of the time which is the point of the discussion, since in both planes there will be certain situations caused by other factors where you dont detect a bandit until its too late.

That is correct, you have the options in the special menu to choose whether you want the hmcs to be display in one eye or in both. Just for your interest RL pilot only see the info in one eye. In my personal case I started using it with VR when that option (in 2 eyes i mean) was not available yet and now i'm totally accoustumed to it, since in both eyes i got a bit more distracted and is harder for me to spot aircrafts covered by the HMCS layer.

I guess the problem is more general than a viper vs hornet scenario, rather that right now viper and hornet are detecting lets say, a mig29 at almost the same distance, while in reality, the hornet should have higher detection range (given same scenario/aspect) based on antena size and power.

Yep, i agree Enviado desde mi SM-G950F mediante Tapatalk

Funny thing, we have other threads suggesting the opposite. From my experience, since the very last update to the 120c, they are on par. The sd10 flies faster in shorter ranges, but the the 120C is actually better at high altitudes and long ranges thanks to the new lofting/autopilot logic. And the CM resistance is higher for the 120C.

Hello, There are some improvements that would make the MP experience much better. I will add some i've been wanting for a long time: Select role GUI: -Show in red and blue allies and enemies airbases, so you dont need to click on them or go to the F10 map to see if you can join a plane based on your coalition -Possibility to sort (excel table style) in the select role GUI. Basically i would love to click on the column where you can see player names so that in the first rows you see the players on the lobby and the bases they are at. Right now if you want ot see where the action is, you need to scroll down the whole GUI and see where players are departing from. F10 MAP: -Similar to Farps where you see right away the coalition, it would be very sweet to see with an icon if a certain airbase is blue or red. It would be great even if it displayed an icon like "under attack" if it has enemy planes in the vicinity (given those planes are detected by any allie). This way you would see if some base need CAP.

I will try that thanks! Enviado desde mi SM-G950F mediante Tapatalk

Yes, i know some servers have that option, unfortunetaly not the ones i play almost exclusively on, like DDCS. In those servers (is common practice not sure why) that omce you put an AI Jtac on the field you start receiving those messages i'm talking about but you cant ever check in with the jtac via radio manu like in SP. Which is also very incovenient. I domt know the reason, i guess it has to do with server performance because in the servers i play there is heavy scripting to make the war almost dynamic. But for sure it would be awesome to have a more refined experience with reachable jtac and coordinates controlled at least from the radio menu. Enviado desde mi SM-G950F mediante Tapatalk

Hello guys and girls, So I was wondering? Why on almost every MP server, when there is a JTAC around you get a message with laser code and coordinates that only last a few seconds, you cant call it back through the radio menu and to make things worst, it gives you the coordinates in Decimal degress and MGRS? Almost any plane in DCS needs coordinates in other formats or does not admit MGRS yet (except for the A10). But what gives me headaches is that you can never check it on the radio menu? Wouldn't be cool if you could access that data with the radio menu, and even better, that it could be displayed in more usable formats? Its not like i dont know how to use a converter, its just that fliying in VR is such an enormous pain in the ass to alt tab out of the game to do the conversion and get back into the game to use the coordinates... Maybe i'm missing some obvious workaround, i dont know...

Given the progress news and if there is no shift in priorities, I would say we probably are at least 12-14 months away from a very EARLY ACCESS FEATURE INCOMPLETE release. And after that 4 years away from an out of EA product (which we know iit does not have to be a feature complete plane). BTW that was not a critic, its was a description of normal product lifecycle in this DCS world.

Now you lost me, the 120c is inferior to what? Enviado desde mi SM-G950F mediante Tapatalk

Well that is a different game, compare to kinematics of the airframes the OP is discussing right? Enviado desde mi SM-G950F mediante Tapatalk

Sorry but that is not totally true, in fact lemoine explain in an article that the f16 is his way to go for bvr, and even describe the f16 as a "rocket ship". Then how much difference this means is a totally different beast. I think we could stop the argument when someone with public documentation or a RL pilot could say some words regarding if that M1.01 limit with pylons is about right or way off. Enviado desde mi SM-G950F mediante Tapatalk

Compared to what? I mean, hornets are known to be very lacking in acceleration and its top speed limit because of the inlet design is M1.8. Obviusly i want a realistic representation, if that means M1.01 with pylon or M1.4 whatever, that should be it. But remember ED have many real hornet drivers giving advice and testing the FM.

This is so true... and so hard to learn... Enviado desde mi SM-G950F mediante Tapatalk

Sublime, are you familiar with cranking, f-pole, a-pole, etc...? I've been killed by sd10 too many tines too know that inside 20nn, its a monster, more if you are at 30k. I usually play at blueflag, 104th, ddcs server, so its against good players, that is true. If you want to get 25mn/30 mn shots i recommend the following rules of thumb 1-Use tws and keep the lock as much a you can 2-be over mach 1 3-loft the shot 4-crank, turn towards the target to loft a shot and crank again, better if you go descending cause you will get a amraam in the air probably 5-dont go in straight line at 30/40k for 40 mn cause you are screaming: i want to shoot you down, the most effective shots are those where your enemy thinks you are attacking another plane or going elsewhere, just to receive an rwr warning with 4 sec defensive time. 6- if you bandit is very high(more than 30k), you can shot way over the rmax and still get him, i've witnessed 40mn kills just because the range seemed so big that the bandit did not expect a shot and once the warning is on, you are too high too defend effectively. Enviado desde mi SM-G950F mediante Tapatalk

I doubt ED does what it does based on wanting casual player to be happy. I just see lack of time and resources for a more complex simulation of certain systems, period.

I didnot know they simulated that in the m2000C and mig21, but i like how it sounds. I would love to have that in other aircrafts as well.

The only thing to fix here as I see are planes on the ground that has not been "cold started" yet. So everything is turned off, hence no heat signature difference from the ground. Bear in mind that this not applies to an aircraft you have just turned off, since your engines and other system will take significant time to get completely cold.

Yes, I kind of agree with nickos86 here. I will say more, i hope they delay the EW modelling on those planes until they can implement something a bit more sophisticated that what we have now in other planes, in which the jammer basically does not add anything in the A2A arena, it will just reduce engagement range againts SAMs. I was under the impression that they were hiring sommeone for EW modelling. I hope that is still true.

I would say that is a bug not fixed. TWS still is "partially" bugged. Enviado desde mi SM-G950F mediante Tapatalk

Yes, its the way that is supposed to be. But a big disclaimer, I wouldn't bet any money that this ED simulating diferences between updates rates (STT > TWS 80 deg > TWS 20 2 bar), but instead it could be just a bug caused by recent changes. Last week TWS was not even updating the amraam and in the intent to fix it maybe there are still things wrong in the code. We will see.