92nd-MajorBug

And just as expected here comes the same useless debate again. That particular horse has been dead for quite a while now. The OP only wanted to know what he could do to see the ball more easily, some settings tweaks and/or using the VR zoom should do the trick, the end.

Not wanting to start a useless debate but 2160x1200 isn't "so bad" compared to my 2560x1440 monitor. And the entry price tag is closer to $400 than $600 right now. But people complaining about VR being so bad are usually those who didn't try it. I know many simmers who tried both options, and only one of them actually went back to their monitor setup.

I have to use the ingame VR zoom to properly see the ball and it works just fine, still way more immersive than the trackIR pancake version

1- The hornet does have a low t:w ratio, that's realistic, 2- You need to be gentler with the stick than other planes, as the hornet will happily go beyond 30° of aoa and stay there while bleeding a ton of energy. If you keep hearing the wind that's not a good sign. All other planes will keep you from doing that with either a limiter or an alarm (or both) I've seen two specific situations that you can get locked in - less than 200kts in descent while pulling hard on the stick, you need to push the stick to get out of it, - more than 450kts with burners and the g limiter active, you can't pull enough Gs to bleed energy and you keep getting faster until you go vertical or throttle back

I've had the same thing happen twice, no stick control after the plane leaves the deck and the FCS doesn't even try to pitch up as it should. The plane just dives into the water. That happened only two times out of about 50 launches so far and I've got no clue as to what caused it. And it wasn't because I'd forgotten to unfold the wings :P I know because I've done that too, and in that case the plane just keeps pitching up

It depends on the weight but usually with everything stable the rpm sits at 88-89%, so maybe with slightly more weight 91% sounds about right. With 8.1° of aoa, full flaps and gear down, the plane has some huge drag. On one hand that limits the number of attempts you can do before you run out of fuel, on the other that means you can get full burners way quicker, should you need them.

More importantly 68% PK in real combat is waaaaaay more than what we get right now against cooperative targets, even at low ranges of about 8 to 10nm. The 7M fired by the F-15C or the Super 530 fired by the M2K are doing great, while the 7M fired by the new hornet is absolute garbage. Now this is early access and it will be adressed at some point in the future - but please don't say the current behaviour is normal or realistic.

Currently every new Hornet we put in the editor has the Blue Angels skin by default, which looks great, but isn't really suited for military ops :P So we can either change it by hand for each plane, or get a dozen Blue Angels because most people don't really pay attention to that in the loadout editor. One very quick and easy way to fix that would be to replace "Blue Angels Jet Team" with "US Navy Blue Angels Jet Team", which would put the skin at the end of the list :)

Is there a template file for the pilot and/or helmet out there somewhere? I've been looking quite everywhere with no success so far. Thanks :)

Does that mean we could be able to use HARMs against airborne radars at some point? :D

(Sorry if this has been reported before, most people have noted that the new model is very costly but nothing specifically about the LODs) The LOD file for the new Hornet seems to have several issues : - Showing the maximum detail model up to 2km seems a little optimistic, - The values aren't incremental (while the LOD files sizes are decremental, as expected) and rather high anyways. model = { lods = { {"fa-18c.edm",2000.000000}, {"fa-18c_lod1.edm",10000.000000}, {"fa-18c_lod2.edm",30000.000000}, {"fa-18c_lod3.edm",75000.000000}, {"fa-18c_lod4.edm",15000.000000}, {"fa-18c_lod5.edm",50000.000000}, }, collision_shell = "FA-18C_Collision.edm", } Compared for example to the much more reasonnable (and fps friendly) Mirage 2000 : model = { lods = { {"M-2000c.edm",50.000000}; {"M-2000c_lod01.edm",500.000000}; {"M-2000c_lod02.edm",2000.000000}; {"M-2000c_lod03.edm",50000.000000}; }; collision_shell = "m-2000c-collision.edm"; } This seems to cause a gigantic triangle count and very poor performance, as shown in this screenshot : https://i.imgur.com/4tTdag2.jpg The black dots on the Al Dhafra main parking are a dozen human piloted F-18Cs. When I look away from them the polycount immediately goes down to a much more reasonnable 400k and fps are back to 45+

Awesome news, thanks a lot :)

Nobody said that :) But still, it's a clue, even if it's not official ;)

"Several new modules being developped by Eagle Dynamics and our partners" is what the promo video says, before listing them all. Most of them are 3rd party modules, so that's not a DCS : Hornet yet ;) What about FC3 ? Aren't they doing a new 3d model and 6dof cockpit for the Su-27 ? ;) I want to believe, but ... feels like it's still too soon ;)

Sorry but I can't find anything official about the F-18C being the next DCS module, except Wags' avatar. Do you have a source for that info ?

Multiplayer including LAN. Which, as someone who does 2 LANs a year in a place with no internet access, I don't find that funny actually.

Hello :) The same problem was already reported here : http://forums.eagle.ru/showthread.php?t=95199

Same here, long burst with the A-10 gun (damn T-80s :D) causing a CTD for me and everyone in close proximity. Same logs, pasting just in case :

Damn I'm stupid. I should have checked that first and somehow didn't think about it, cause usually we have to edit fuel and payload at mission start - in this mission everything was already done. Tested after switching the base to blue and it works perfectly - you may close or delete that thread, sorry for the inconvenience.

It's even better when you look : they didn't manage to install it (ok, shit happens), then they didn't bother to register here because they didn't want to (what ?) and then they throw out a little tantrum on Amazon comments instead. So : whiney little kids :)

Nope, I just see the "repair" subtitle in the top left corner (with no sound - but the sound was already absent in 1.2.0 and the repair worked) Edit : the automatic repair worked in 1.2.0 but I'm not so sure about the interphone option - squad mates are being positive that it didn't work in 1.2.0 either

It seems that the repair at parking in 1.2.1 is broken. Tested in MP (with the latest update), with engines running, then engines off and apu running, then with everything off, cockpit opened or closed, the repair timer doesn't show and no repairs ever happen, either automatically or by asking the ground crew with the interphone.

Just read the 1 star comments - they are priceless :p

You're a nice dude so I'll assume that you are not trolling me :)

See what I meant ?