All Activity

Я всегда выставлю QFE цели, привычка с Виггена и Мигаж F1. Но тут такой номер не прошел, если недолет с QFE, значит высота цели еще меньше, у меня при высоте цели в 280 метров при угле атаке в 40 градусов и заходы с 4км до 2км и скорости выхода в 850 км/ч конкретный недолет от 200 - 400 метров

+1 for this.

Yeah, I'm following your posts in this! Like your dedication! [emoji1303] Sent from my SM-A536B using Tapatalk

Nah, thats not it, not in the quick mission I tried this and where track is from, anyway... the targets are on coastline flat area so maybe few m difference at most, which should not be the cause of it. My guess is, looking at that screenshot of HUD, that aiming reticle and line are shifted above horizont line, I think the top of the line should be level with aircraft line, not anove it, and if you shift that line down to the aircraft line on the HUD the aiming circle comes right above the area where the bombs actually hit. I'm at work right now so can't post a screenshot of what I mean, I'll get to show it tomorrow. Yes, good point

Personally, I prefer using bases/grips/extensions that are compatible with Thrustmaster connectors. (Virpil, Rhino, FFBeast, Moza and more). But yes, of course you could sell parts when you upgrade. There are converters available for matching unmatching grips. If I were you, I would look up the different forum threads under the Input forum to seek more advice there! Also under the "For Sale" thread, you can find kits for Rhino and FFBeast, which makes the DIY process quicker and simpler. [emoji4] Cheers! Sent from my SM-A536B using Tapatalk

Я проверял, что для ППМ в районе цели в DTC выставлено правильное превышение, прилетал к цели проходил на бреющем, чтоб выставить на местный QFE, вот правда что я не сделал пока, так это не выставлял QNH, раз цель занесена с превышением. Правда мне кажется всё это некорректным, так как тут должна работать простая геометрия, мол угол пикрования от КВ(курсо-вертикаль) и наклонная дальность берется от ЛД(лазерный дальномер), это ж не Ми-24 с его АСП17 без ЛД. Короче попробую с QNH ещё Только я пишу лайф с первого дубля) Стабильность - признак мастества;) Я вот пока так и не понял в чём там собака зарыта..

Guys shouldn't the target's altitude setting be ignored all along with laser rangefinder working? There is no mention of it in combat employment manual, and, say, in MiG-21 target elevation is only needed when radar rangefinder is off.

@MAXsenna thanks for reply! Do you think if Winwing release FFB base it will be compatible with current joysticks? In such case I could just sell ORION 2 base and buy new one.

Absolutely. Amen, Devil. As the newcomer to the group all I can say is Zipper will be missed greatly. The missing man formation takes on a whole new meaning for me. He welcomed me to the group some 2 years ago and made me feel welcomed immediately. So happy my work travels allowed us to meet in person. RIP, brother Zipper.

Thread wasn't moved, so I posted a new bug report in the Game Crash section: @Maverick Su-35S If you happen to have a crashdump, please post it there.

The DCS client and server quit with a "Login session has expired" popup when reconnecting to the master server after the connection had been lost for about half an hour. Said quitting now appears to trigger a delayed segmentation fault. Originally reported here. Full crash dump: dcs.log-20251003-120952.zip Annotated excerpt from dcs.log: # tabbing in and out, everything works prior to computer suspension 2025-10-03 11:15:20.855 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [2560, 1440] 2025-10-03 11:15:22.549 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2025-10-03 11:16:57.822 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [2560, 1440] 2025-10-03 11:17:02.051 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2025-10-03 11:21:16.576 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [2560, 1440] 2025-10-03 11:21:17.875 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] ... # coming back up from suspension, the session check fails immediately 2025-10-03 12:06:56.534 ERROR ASYNCNET (2808): HTTP request dcs:checksession failed with error 6: Could not resolve hostname 2025-10-03 12:06:56.535 WARNING ASYNCNET (2808): Session check failed: -6 ... # a minute later, DCS decides to terminate, but lets me tab in and out anyway 2025-10-03 12:07:57.966 ERROR ASYNCNET (2808): The session has expired (401). Exiting... 2025-10-03 12:07:57.972 INFO EDCORE (Main): (dDispatcher)enterToState_:5 2025-10-03 12:08:38.747 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [2560, 1440] 2025-10-03 12:08:42.582 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [0, 0] 2025-10-03 12:09:42.972 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [2560, 1440] 2025-10-03 12:09:48.735 INFO APP (Main): application shutdown ... # two minutes later, DCS suddenly SEGFAULTs 2025-10-03 12:09:49.196 WARNING SCENE (8972): Scene was removed with 1 alive objects 2025-10-03 12:09:49.210 INFO WorldPlugIns (Main): Deinitializing plugins... 2025-10-03 12:09:50.441 INFO TERRAIN (Main): lSystem::exit() 2025-10-03 12:09:50.443 INFO TERRAIN (Main): lSystem::CleanScenes() 2025-10-03 12:09:50.443 INFO WORLDGENERAL (Main): TerrainUtility:: updated in parallel: 0, updated in the main thread: 0 2025-10-03 12:09:50.504 INFO INTER (8972): ITerrainGraphicsEntryPoint::close() 2025-10-03 12:09:50.564 INFO INTER (Main): ITerrainEntryPoint::close() 2025-10-03 12:09:51.160 INFO INTER (Main): ITerrainGraphicsEntryPoint::close() 2025-10-03 12:09:51.160 INFO INTER (Main): ITerrainEntryPoint::close() 2025-10-03 12:09:51.161 INFO EDCORE (Main): try to write dump information 2025-10-03 12:09:51.163 WARNING SCENE (8972): Scene was removed with 5 alive objects 2025-10-03 12:09:51.271 INFO EDCORE (Main): # -------------- 20251003-120952 -------------- 2025-10-03 12:09:51.273 INFO EDCORE (Main): DCS/2.9.20.15384 (x86_64; MT; Windows NT 10.0.19045) 2025-10-03 12:09:51.275 INFO EDCORE (Main): C:\Games\DCS World OpenBeta\bin\lua.dll 2025-10-03 12:09:51.277 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ff9994817d0 00:00000000 2025-10-03 12:09:51.279 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'C:\Games\DCS World OpenBeta\bin;', symOptions: 532, UserName: 'user' 2025-10-03 12:09:51.281 INFO EDCORE (Main): OS-Version: 10.0.19045 () 0x100-0x1 2025-10-03 12:09:51.282 INFO EDCORE (Main): 0x00000000000017d0 (lua): lua_gettop + 0x0 2025-10-03 12:09:51.284 INFO EDCORE (Main): 0x00000000000761eb (edCore): Lua::Config::Config + 0x1B 2025-10-03 12:09:51.286 INFO EDCORE (Main): 0x0000000000a980de (DCS): SW + 0x47BEAE 2025-10-03 12:09:51.286 INFO DX11BACKEND (8972): DX11Renderer::shutdown() 2025-10-03 12:09:51.288 INFO EDCORE (Main): 0x0000000000a97c32 (DCS): SW + 0x47BA02 2025-10-03 12:09:51.290 INFO EDCORE (Main): 0x0000000000a9078b (DCS): SW + 0x47455B 2025-10-03 12:09:51.290 INFO EDCORE (Main): 0x0000000000a45aaf (DCS): SW + 0x42987F 2025-10-03 12:09:51.291 INFO EDCORE (Main): 0x000000000015a56a (Visualizer): smSceneManager::DestroySceneManager + 0xCA 2025-10-03 12:09:51.291 INFO EDCORE (Main): 0x0000000000a66f36 (DCS): SW + 0x44AD06 2025-10-03 12:09:51.291 INFO EDCORE (Main): 0x00000000025b8da1 (DCS): AmdPowerXpressRequestHighPerformance + 0x1097D9D 2025-10-03 12:09:51.291 INFO EDCORE (Main): 0x00000000010dac82 (DCS): SW + 0xABEA52 2025-10-03 12:09:51.291 INFO EDCORE (Main): 0x0000000000017374 (KERNEL32): BaseThreadInitThunk + 0x14 2025-10-03 12:09:51.504 INFO EDCORE (Main): Minidump created.

Well there is no MFD in the first place, so yeah no pages either. But instead, we have multiple speed indicators and displays of any kind and so on, a "Uhrenladen" as we say, which normally is anything but clear and understandable.

Have you tried to find the barometric altitude of the target in QFE at which you will hit the target? And compare it with the altitude of the target itself, is there a big difference? You can look at the post above to understand what I am talking about

Ya... without porting TrackIR/VR and lots addons for the UI client, and just the server side may be doable to implement first.

Well, it always has the certain penalty that runs the mediator to do the execution translation between Linux kernel and app.

The D model.

There is an Action in the Mission Editor Trigger menu called "X: Set Command". Use this Action with the value: 246, it will set the time back to normal.

I've seen in some of the campaigns from baltic dragon, the mission itself sets time compression to normal before important messages/callouts etc. I can not find any suitable Action that fits this. Anyone knows how to do it?

The dedicated server actually runs hassle-free on vanilla Wine. Unfortunately, the performance is worse than Windows on bare metal. Coincidentally, Wine 10.16 with upstreamed NTSYNC support came out last week. I'm expecting/hoping/praying for that to make a significant performance impact, but I haven't had the time to run new benchmarks.

The problem is that somehow the TrackIR is switched back to the "Default" profile when I run DCS World. I saw this after exited from the game. And I think I have found out how to prevent this: I ticked the "Exclusive" checkbox in TrackIR. Tried with two different modules and it works as before now.

Which model of Tomcat? Thanks.

I've had this before. There is some checkbox in the TrackIR driver that you can use to just force the profile you want, instead of allowing TrackIR to pick the profile based on the game you're playing. Unless you have the situtation where DCS is trapping the assigned keys for Pause and Center due to double mapping, I'll bet thats what it is.

I've never assigned or un-assigned keys in DCS regarding to TrackIR. I don't use the Keyboard but Joystick bindings though for re-centering. What happened sometimes to me is, that the key identifier was wrong when I plugged in the device AFTER I started TrackIR for some reason. (But then it didn't work in TrackIR either iirc). Don't know of this is of any help though, sorry.

I use Arrow Up for my center view since it seems universally assigned in flight sims for plane control, which I don’t use. Plus it’s easy to find. Now that I read this I don’t recall deliberately un-assigning this in DCS. Have you tried simply using a different key? Just to test. (Oh I see you tried F12) Could “-“ be hard bound somehow? Maybe check the General category as well as the aircraft module.

@QuiGon That makes sense! [emoji1303] Sent from my SM-A536B using Tapatalk