dorianR666

no

you mustnt touch your stick or pedals - at all. if they get out of deadzone, the alignment is ruined. some people on reddit also claim that strong wind can ruin it but i havent seen that happen.

but then its still a bug i dont think the real f-15e would show crimea before being aligned lol maybe it shouldnt show anything, or show 0 longitude 0 latitude, or the inserted coords. but not the dcs maps 0, 0.

if my game sometimes waits tens of seconds to process one frame, then even if i had 100 cores or threads it would still be a slideshow. the problem is something else. i have seen this too, in the same situation. i will try your fix, thanks

same

if you bring down mfcd contrast and brightness, the flight plan becomes actually visible.

this is what HRM looks like on AMD 1600X sometimes had to kill the game from task manager because the fps was so low (>minute per frame)

theyre on discord

thats likely HW failure then weak power supply? overheating?

when you start the MFD recording, it actually generates a PNG file of the MFDs content every 5 seconds in your screenshot folder

yeah its broken, offset points too

Is there truly no way of making the F-15E throw only flares or only chaff? 1) modifying ALE45_PRG.lua has no effect 2) semiauto mode is not implemented 3) the default MAN1/MAN2 in man mode throws both flares and chaff 4) there is no in-cockpit way of modifying MAN1/MAN2 5) moving the rear cockpit DISP SEL switch to chaff or flare positions still throws both flares and chaff am i stupid or what

why should it? there is no reason for it. remember: this hud doesnt have flight path vector. so there is nothing to be gained by having the ladder matched to horizon. this is simply attitude indicator on collimated display, so you dont have to look down on an instrument all the time. this is actually how the jets of this era used to be, its normal. f-14a/b hud looks the same.

why should there have to be a usecase for this maneuver? this is a sim. if something behaves (supposedly, i cant judge it) unrealistically, then its a bug. it doesnt matter that the activity is unusual IRL.

i dont think this is even implemented

my cpu is amd 1600x, released in 2017. amd's currently most powerful pc cpu is 7950X3D, released this year. https://cpu.userbenchmark.com/Compare/AMD-Ryzen-9-7950X3D-vs-AMD-Ryzen-5-1600X/m2052977vs3920 unless your software paralellizes the load equally over more than 12 threads (rare and never seen in games), then performance only doubled... in 6 years. (btw less than doubled in single core). for 6 years, thats woefully little in my book. those cpus came out in q2 2020. the second paragrah wasnt directed as you, which is why i separated it with newlines. i didnt make that clear, my bad.

transistor count. computational power of cpus definitely doesnt double every 18 months. it grows woefully little actually. hardware requirements need to be more detailed than just "i3 at 2.8 ghz", thats extremely vague. also its a common practice for games or multimedia software to use optional instruction set extensions only when available on that particular pc, defaulting to standard amd64 instructions when not available. i agree the potential customer should be informed of this. even modern cpus sometimes dont support avx: https://news.ycombinator.com/item?id=24578591

still bugged...

why would interference make the antenna stop moving? obviously this is a bug. also notice the values in top left corner became nonsensical and its walking through bars extremely fast. the scan pattern got stuck at 0 degree width.

it doesnt lock anything. thats designation (L&S). nothing is locked. designation only tells the plane which target you consider as the most important one. lock is stt. in tws, as long as there is a trackfile, there must be a designation. this is a new change in dcs and thats how its supposed to work. there is nothing wrong with this happening.

why is this marked "correct as is"?

f-16 does not correlate iff returns to tracks.

i wonder if gimbal limits of AG radar will be implemented currently you can fly straight up and still be able to map the ground below you lol

dcs hornet doesnt simulate multiple close targets merging into one contact, so raid is actually entirely useless.

if youre moving tdc vertically on attk rdr, the shape of the scan volume doesnt change. therefore nothing in az/el should change either. that is correct. the problem is something else, there is some kind of a math bug in calculation of the bottom and top yellow lines of the box. perhaps it doesnt take into account that bars are overlapping, making the box larger than correct.