Cobra847

The two bugs in this thread do not seem to be reproducible atm.

Not an F-14 bug. Not sure why your axes are being reassigned. Unpause the sim so that the LoD changes. You can pause it once the RIO panels appear. Not really a bug. Engine limitation.

There are a few scripts that some servers run that breaks with feature.

The G-Meter is top left of the main instrument panel IIRC.

Thank you! :) awesome shot too!

BTW for Iceman's helmet; try modifying the RoughMet as well and make the Blue channel (metallic) brighter. IIRC his helmet had a metallic specularity response.

We're aiming for this week on the paintkit. Stby gents!

When does this happen?

A couple of quick notes: -The lofting desynchronization issue is not our bug. We reported it months ago to ED because we knew it would be an issue in MP servers, but it's not fixed yet. -We have very little control over missiles once they leave the aircraft. We've been hoping to get more direct control over ordinance to no avail. I'll see if this bug is on our end or somewhere in the DCS missile code.

Thank you! :)

Improvements will be made until we are satisfied. Most of the data points in our automated testing are very close to the real aircraft. At some point we will publish these. Obviously bugs or inconsistencies in the model will be corrected as well. We also get feedback from our F-14 Pilot SMEs practically every day. These are mostly micro-tweaks at the moment to reproduce the exact flight characteristics found from a pilot perspective.

It might work fine if you uninstall the mod, repair and then re-apply the mod.

With regards to AIM-54; here's our Phoenix whitepaper: http://media.heatblur.se/AIM-54.pdf If our implementation differs from the results of this research, we will of course adjust it appropriately to maintain Multiplayer cohesiveness & realism.

This is a flawed analysis because we emphasize detail for the player's aircraft, but go to great lengths to optimize every other F-14 in the mission/server at any given time. Of course, as DGambo noted, one concession that we have made is a lower than usual number of visual damage zones. :) F-14 at LoD 1 (All aircraft >100m) - 8 Mb F-18 - 24 Mb ----- Triangles (Pretty unimportant metric on a GPU in 2019) (at similar visibility ranges) F-14B @ LoD 1 - 348 706 F-18 @ LoD1 - 196 000 ----- Drawcalls F-14 @ LoD1: 54 F-18 @ LoD1: 265 With regards to RAM usage; this is fixed in the next patch. We're waiting for it to be released. It's related to DCS loading and uncompressing all sound files on mission load. With regards to the Cockpit; most of the RIO pit is actually hidden when flying in the Pilot's seat. Thus, the numbers you get by using the modelviewer are not quite accurate. :) Hope that helps to elaborate on performance focuses for the F-14

Infinity, IIRC. It'd likely be useless otherwise owing to parallax.

The OST is not unrelated. I'd prefer to distribute it in .wav instead of lossy formats. We're in the days of AAA games taking 100Gb+ once installed. I don't think 8GB is too much to ask for. :) I know it's a bit of a pain, but we can't really do that much about this. I do agree that the manual need image compression though

Not a bug per se but a good suggestion!

Marked as no bug- but will track this and add to suggestion/feature improvements

Remove mods & try a repair :)

Hey Everyone! Thank you for helping us refine the F-14 and improve the aircraft! We really appreciate it. From today we will start tagging and tracking bugs. Those bugs verified to be errors will be transferred to our internal bug tracker and fixed. You'll see these tags appear in brackets edited into the title of your bug report. Please try not to take it too personal if your bug gets marked as [NO BUG] or similar and you're sure it's actually an issue. We'll undoubtedly make mistakes - just raise it to our attention and we'll re-evaluate :) We do, however, appreciate double checking the manual and other bug reports to ensure that the issue you're reporting is actually a bug. It will save us time! After some time, [NO BUG] threads will be deleted. Suggestions posted here (or feature requests) will be moved. Thank you again for all of your help, Sincerely, HB

Check if you have a double input binding. I'm marking this as no bug for now as it's exceptionally isolated. Let us know!

The FM does take into account these, but the way they're applied to the aircraft means their weight won't show up properly.

Спасибо! We have to investigate Block 2 more closely. For some reason fuselage damage is not seen as critical for the AI. In the human aircraft, we detect this and kill systems/introduce hydraulic/electrical/fuel leaks as appropriate.

This points to IMU/INS issues. :) Unlikely to be a bug.

AB IR coeff changed to 2.5. I can't google translate the video.