Flagrum

Yeah, what do those filthy casuals even think what DCS is about? It's called Digital Cold Start for a reason...

With the Harrier or the F-18 I don't have it either. This and your experience tells me this: something is weired with the F-14. I know why my F-14 is lagging so bad: my system spends most of the time fiddling around with the page file, swapping stuff in and out. I assume, it is the terrain textures, that change when flying over ground and that need space in RAM - and therefore other stuff has to be parked on the page file. So, what is clogging up my RAM so that no terrain textures fit in anymore? You have 32 GB RAM - double the size of mine. That might actually help a lot, I guess. But on the other hand, all other modules are performing much better for me, even with "only" 16 GB.

After todays update: Loading times seem to be substancial better than before, but you really, really, REALLY notice that the F-14 is meant to be flown in a maritime environment. As soon as dry dirt is appearing beneath the aircraft, the slideshow begins. Tried Caucasus now, as the Persian Gulf was not much better than before. Leaner terrain textures ... that was my hope. Tried to bomb the abandoned airfield, coming from the sea. Rolling in was like 20° roll, 10 sec pause, another 25°, 20 sec pause, 50°, 15 sec pause, omg, must correct ... holding stick still for 30 sec, roll 60° in opposite direction, etc. un. fly. able. Gave up, killed DCS with the task manager (that's 5 minutes faster than windows orderly releasing 16GB of RAM that is parked on the pagefile.sys). Might try later again, but you might have guessed it, I am a bit too annoyed right now.

Death Valley. Fun-Fact: Death Valley liegt sogar tiefer als 0 MSL - und das hat zu beginn zu DCS crashes geführt, wenn man unterhalb des Meeresspiegels geflogein ist. ^^

I can't think of any situation where sliding/gliding on melted rubber would be more effective than a few percent less braking effectiveness compared to a "perfect braking" (which neither ABS nor humans could probably archive anyways).

Looked still wrong to me - the ASL was still swaying left and right a lot. The ASL also never really coincidented with the target marker, even when he dropped the weapon, he was heading about 10-15 degree right according to the ASL - but thanks to laser guidance he still got that kill.

You should consider making stand up comedy as your way of making a living.

(https://forums.eagle.ru/showthread.php?t=235973) Wohoo! :thumbup: Looking forward to it!

After todays hotfix it seems that ED changed when the "Fly!" dialog appears during the loading process of a mission. Before, it already showed up although seemingly not all loading was finished. That probably lead to many concurrent load attempts of all kinds of stuff - fps dropped. Now the "Fly!" dialog just appears after all loading really has been concluded - and voila, the F-14 is now more responsive. But the load time is still the same for me - now I am just forced to really wait until DCS is ready to go. So, that was not really a fix of the problem, I think. While I was waiting for the "Fly!" dialog to eventually appear, I monitored my system (Ressourcemonitor of Win7): the majority of the time the system was bussy accessing all kind of texture .dds files of the F-14. And it was constantly swapping memory out to the pagefile - which costs an additional heck of a long time- 2019-03-18 17:36:50.142 INFO VISUALIZER: Preload() camera=-159595.570872, 5047.189476, 63359.535720 radius=34500.000000 2019-03-18 17:36:50.142 INFO EDTERRAINGRAPHICS41: ITerrainGraphicsImpl4::forceLoading(): pos=(-159596, 5047.19, 63359.5), radius=34500 2019-03-18 17:36:51.528 INFO EDTERRAINGRAPHICS41: surface5 clean up LOD 0: left 4 released 80 2019-03-18 17:36:51.528 INFO EDTERRAINGRAPHICS41: surface5 clean up 774.886873 ms 2019-03-18 17:37:36.137 INFO EDTERRAINGRAPHICS41: surface5 clean up LOD 1: left 8 released 76 2019-03-18 17:37:36.137 INFO EDTERRAINGRAPHICS41: surface5 clean up 4729.904429 ms 2019-03-18 17:37:40.891 INFO EDTERRAINGRAPHICS41: surface5 clean up 0.000311 ms 2019-03-18 17:37:44.730 INFO EDTERRAINGRAPHICS41: surface5 clean up 0.000000 ms 2019-03-18 17:39:02.166 INFO GRAPHICSVISTA: Creating Resource "Unicode" of type 1 2019-03-18 17:41:23.535 ERROR_ONCE DX11BACKEND: texture 'bake2pan_normals' not found. Asked from 'NGMODEL' 2019-03-18 17:49:36.999 INFO VISUALIZER: Preload() finished Just look at the time stamps at the end ... To me, this looks like DCS is trying to squeeze in all the F-14 textures, but can't. So it swaps out other stuff to the page file. When I then fly over PG landmasses, everytime DCS loads further map data, it first accesses the pagefile - to swap out some other less important stuff. So ... all the F14 textures seem to clog up my system REAL good... System: i5 2500K, 3.2 GHz, 16 GB RAM, GTX970, DCS on SSD

Different reflectivity for radar waves of water and ground?

It should be like this: http://www.heatblur.se/F-14Manual/emergency.html#engine-airstart

It should be ok thought to state the title of the manual and the chapter or page where someone can find the image.

fwiw, this behaviour is documented in NAVAIR 01-F14AAP-1, ch. 2.32.5

You could still post the title of that "online manual" so that people could search for it for themself.

I totally agree on point 1! This is really annoying ... Regarding #2: Agree here as well, although you can close the menu without selecting any option by "selecting" the center of the menu. But a dedicated button for that would probably more ergonomic.

Letting DCS rebuild the shaders made no real difference for me. It is still the same: the more terrain around the plane, the choppier everything gets. (Persian Gulf map) I now suspect it is indeed a memory issue rather than the radar code. The pagefile, although managed by the system, was 100% full (but not growing!?). I need to check that more in detail later/tomorrow. But an option for medium size cockpit textures would probably be a good idea - the almost 4 GB video RAM of my GTX970 is probably 90% filled up with 4K F-14 textures ...

My experience is similar so far. I suspect it's the radar code and Lantirn probably as well. FPS drops to 1-2 fps in the RIO pit with Lantirn active and when new terrain is ahead. Flying back, over already loaded terrain, it is a bit better. Need to test more, though, but double-checking with a quick jump into the FA-18 (same mission, same route, no lantirn though ofc) gave me the expected 30-40 fps.

@ the "Who cares?"-faction here ... he just made a suggestion in the hope that people might consider it. You disagree? Fine, then don't consider it. But wtf is the point here in actively fighting against his suggestion? Seems that YOU care way too much, not the OP. *facepalm*

... and the manual is available for a few weeks now.

If this is not a bug, then the mode designated as "backup mode" - the least practical mode - is the default? Seems strange to me - does anyone have a source for this?

The guy operating the cat is AI. And the AI usually trusts us humans. It probably thinks, "well, he's a homo sapiens - he probably has a good reason for whatever he is trying to do there ..."

Yes, the flight lead is aircraft 1 of a flight of up to 4 aircraft. You can set the "Player" skill to any of them - i.e. you can be No. 2 and No. 1 can be AI. But what draconus said is also true - don't expect much from the AI, especially as flight lead. They may follow the route set in the ME and do all the tasks that are set for the waypoints, but communication is probably veeeeery limited from their side.

That channel is linked to the freq. that you set for the whole flight. That probably overrides your settings.

I only know about is, that they use a work-around for the micro switches in the pedals. As consumer grade pedals are not trimmable (i.e. no FFB pedals), the sim assumes that the feet rest on the pedals if the axis is not centered.