All Activity

Mine is packed and ready for shipment (from a local dealer/warehouse). Ordered sometime in April. So hopefully I will have mine before the weekend - as a best case scenario that is

This is SNR-125 (SA-3 target tracking and fire control radar). It does have TV channel IRL, as well as thermovision on later upgrades. The TV channel can be used for silent tracking, but the SAM itself requires the radar to lock and track target afterwards. The SAM itself transmits the commands to the seeker, which arms ~450m before the impact the fuze gets activated and will trigger explosion within the 45m of the target. Only small number of batteries had thermovision in 1999 (possibly only 1), since the already purchased upgrade kits were resolved before the war to Egypt. I am curious to find out who was the person who pushed and authorized this. However in DCS this SAM has no TV sensor implemented (checked in LUA). Also missing is the control cabine as well as power supply which are deployed in close proximity of the SNR-125. Other SAMs which should, but do not have have this DCS: - SA-6 (e.g. capable of passive LOAL launches IRL!) - SA-8

True but that would require a very high res screen ie Apple “retina” level. Or a very small or far away display. At normal sizes and viewing distances even a 4K screen needs AA to remove jaggies. Most gamers use 1080p and 1440p. Not sure why this requires explaining as it’s all fairly obvious. Suit yourself but to me AA Off looks like hot garbage.

I would quite happily pay a subscription fee, knowing it would be used on core advancements and things that don't have a direct ROI.

@shaji I saw this crash (repeated) on a dedicated server running the MarianasWW2 map, reported it, and it hasn't happened again recently. Just speculation, but I think that some updates to the Essex carrier, including specifying it's draft (which was missing), may have been the fix in our case. It's hard to know as it isn't spelled out in the patch notes every time that update x fixes crash y. It might be worth looking at any ships in your mission, their waypoints, and the sea depth in those areas for some sort of clue as to what might be causing the crash. Good luck.

Hello, I see that the midweek offer offers discounts of up to 50% for the DCS: AH-64D Apache, which is usually $79.99. I found it at $63.99, so it's nowhere near 50% off, which should bring it down to $40! Am I wrong?

It has for over 10yrs in DCS.

When running missions on a dedicated server clients see the AI on deck in a 2-point attitude (and main gear partially sunken into the deck):

Great, with your prayers, comrade supersonic!

Well, as you write, these are advanced options, in other words - for people very savvy in IT and Windows aspects. Remember, however, that many people have very basic knowledge of how the system works and expect software to be a complete package with the most important functions, leaving nothing else to be touched. Adding a File Manager to the DCS Launcher isn't quantum physics or a rocket science. ED should have done this, and in my opinion, it's losing out significantly, as some people have stopped buying new maps due to disk space issues, or rather, the lack of it. Personally, I don't have a problem with this because I replaced the DCS drive with a 4TB NvMe last year so it will last for a while and I only have DCS here However, not everyone has such opportunities and these people should be remembered.

Don't advocate for others...others will do it themselves if feel as needed. Out and over

Sorry, again this is off topic, but this is another example of why developing an F-35 for DCS is not a good idea. The development of this type is used every time as a reason why something else must not be as "realistic". Apart from the fact that this is not a valid argument, DCS is committed to being as realistic as possible. Therefore, in my opinion, it is only right to either adapt the Lightning Pod accordingly, or to develop a Lantirn Pod for the F-16 (as close to reality as possible) and replace the current Lightning Pod with it.

I'm sorry, but this is a completely different error you'rer eferring to in `KERNELBASE.dll`, ours happen while flying and in MP, please create a different forum post for it to avoid confusion. Thank you.

Folks this thread is starting to go off topic now. But as a reminder DCS will always try to be as real as possible, but we can only use public, unrestricted and unclassified data. DCS is for entertainment purposes. thank you

Thank you!

Apologies for going off topic but this is an interesting deviation. I understand your need to have a simulation of combat aircraft. However, DCS isn't simulating this. It does it's best to get a 'realistic representation. However, even with 'study level' aircraft some systems are not simulated because of technical capabilities or military/commercial secrecy. Therefore, in my opinion the blanks need to be filled in anyway, or you are not getting an aircraft near the functioning aircraft real pilots fly in real life. Take the recent announcement of ED's F35. It can only really be an educated guess as to its RCS. Equally ED have to take the same educated guess on how some smart weapons are programmed and work. I've long stopped calling for a simulation and instead I'm calling for a realistic combat flight game. That I can enjoy, that's complicated enough to engage with but doesn't feel like its a place of work either, with all that entails.

I'm seeing exactly the same type of errors, happens to me when I launch the game from the UI launcher, crashes when selecting launch game. If I disable the UI launcher the problem appears to go away, this is 100% reproducible for me. === Log opened UTC 2025-07-29 09:49:55 2025-07-29 09:49:56.156 INFO EDCORE (Main): Platform Timer Resolution: 15.73ms 2025-07-29 09:49:56.651 INFO EDCORE (Main): Created boot pool: n:20 2025-07-29 09:49:56.652 INFO APP (Main): Command line: "D:\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" 2025-07-29 09:49:56.652 INFO APP (Main): DCS/2.9.18.12722 (x86_64; MT; Windows NT 10.0.26100) 2025-07-29 09:49:56.652 INFO APP (Main): Application revision: 252722 2025-07-29 09:49:56.652 INFO APP (Main): Renderer revision: 26305 2025-07-29 09:49:56.652 INFO APP (Main): Terrain revision: 26363 2025-07-29 09:49:56.652 INFO APP (Main): Build number: 364 2025-07-29 09:49:56.652 INFO APP (Main): CPU cores: 10, threads: 20, System RAM: 65363 MB, Pagefile: 4096 MB 2025-07-29 09:49:56.652 INFO APP (Main): CPU info: system affinity mask: 11111111111111111111 process affinity mask: 11111111111111111111 CPU: Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz [1x L3 caches] CPU has uniform cache size 20 MB (per cache) all CPU cores have the same efficiency class 0 all CPU cores have the same performance class 0 common cores: {10, 11, 12, 13, 14, 15, 16, 17, 18, 19} render cores: {0, 1, 2, 3, 4, 5, 6, 7, 8, 9} IO cores: {} unavailable cores: {} pause10: 0.031243 us (std dev: 0.018180) pause10: 1144 cycles (std dev: 704.0) 2025-07-29 09:49:56.765 INFO EDCORE (Main): Loaded D:/Eagle Dynamics/DCS World OpenBeta/bin/edWebViewBrowser.dll 2025-07-29 09:49:57.708 INFO ASYNCNET (20116): Login success. 2025-07-29 09:49:59.490 INFO ASYNCNET (20116): Got auth data. 2025-07-29 09:51:20.073 INFO EDCORE (Main): signal caught: 'Abnormal termination' 2025-07-29 09:51:20.073 INFO EDCORE (Main): try to write dump information 2025-07-29 09:51:20.098 INFO EDCORE (Main): # -------------- 20250729-095121 -------------- 2025-07-29 09:51:20.099 INFO EDCORE (Main): DCS/2.9.18.12722 (x86_64; MT; Windows NT 10.0.26100) 2025-07-29 09:51:20.100 INFO EDCORE (Main): C:\WINDOWS\System32\KERNELBASE.dll 2025-07-29 09:51:20.102 INFO EDCORE (Main): # FFFFFFEA (Unknown exception code) at 00007ffcb6ff7f9a 00:00000000 2025-07-29 09:51:20.103 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'D:\Eagle Dynamics\DCS World OpenBeta\bin;', symOptions: 532, UserName: 'pyate' 2025-07-29 09:51:20.105 INFO EDCORE (Main): OS-Version: 10.0.26100 () 0x100-0x1 2025-07-29 09:51:20.106 INFO EDCORE (Main): 0x00000000000c7f9a (KERNELBASE): RaiseException + 0x8A 2025-07-29 09:51:20.107 INFO EDCORE (Main): 0x0000000000006a19 (edCore): ed::current_exception_stack_trace + 0x279 2025-07-29 09:51:20.108 INFO EDCORE (Main): 0x00000000000c1989 (ucrtbase): raise + 0x1D9 2025-07-29 09:51:20.110 INFO EDCORE (Main): 0x00000000000a4ab1 (ucrtbase): abort + 0x31 2025-07-29 09:51:20.110 INFO EDCORE (Main): 0x00000000000c19de (ucrtbase): terminate + 0x1E 2025-07-29 09:51:20.110 INFO EDCORE (Main): 0x0000000000001943 (VCRUNTIME140_1): (function-name not available) + 0x0 2025-07-29 09:51:20.111 INFO EDCORE (Main): 0x00000000000021af (VCRUNTIME140_1): (function-name not available) + 0x0 2025-07-29 09:51:20.111 INFO EDCORE (Main): 0x000000000000220d (VCRUNTIME140_1): (function-name not available) + 0x0 2025-07-29 09:51:20.111 INFO EDCORE (Main): 0x0000000000004082 (VCRUNTIME140_1): __CxxFrameHandler4 + 0xB2 2025-07-29 09:51:20.111 INFO EDCORE (Main): 0x000000000016650f (ntdll): __chkstk + 0x9F 2025-07-29 09:51:20.111 INFO EDCORE (Main): 0x0000000000074527 (ntdll): RtlWow64GetCurrentCpuArea + 0xC17 2025-07-29 09:51:20.112 INFO EDCORE (Main): 0x00000000000733b6 (ntdll): RtlRaiseException + 0x206 2025-07-29 09:51:20.112 INFO EDCORE (Main): 0x00000000000c7f9a (KERNELBASE): RaiseException + 0x8A 2025-07-29 09:51:20.112 INFO EDCORE (Main): 0x00000000000052c7 (VCRUNTIME140): _CxxThrowException + 0x97 2025-07-29 09:51:20.112 INFO EDCORE (Main): 0x000000000002a085 (edCore): ed::SQLite3::Cursor::column + 0x115 2025-07-29 09:51:20.113 INFO EDCORE (Main): 0x000000000002a32b (edCore): ed::SQLite3::Cursor::step + 0x3B 2025-07-29 09:51:20.113 INFO EDCORE (Main): 0x0000000000aa7cd0 (DCS): SW + 0x490BD0 2025-07-29 09:51:20.113 INFO EDCORE (Main): 0x0000000000a930d9 (DCS): SW + 0x47BFD9 2025-07-29 09:51:20.113 INFO EDCORE (Main): 0x0000000000a93754 (DCS): SW + 0x47C654 2025-07-29 09:51:20.113 INFO EDCORE (Main): 0x0000000000a90468 (DCS): SW + 0x479368 2025-07-29 09:51:20.113 INFO EDCORE (Main): 0x000000000258a307 (DCS): AmdPowerXpressRequestHighPerformance + 0x1084303 2025-07-29 09:51:20.113 INFO EDCORE (Main): 0x0000000002584a17 (DCS): AmdPowerXpressRequestHighPerformance + 0x107EA13 2025-07-29 09:51:20.114 INFO EDCORE (Main): 0x00000000010c5632 (DCS): SW + 0xAAE532 2025-07-29 09:51:20.114 INFO EDCORE (Main): 0x000000000002e8d7 (KERNEL32): BaseThreadInitThunk + 0x17 2025-07-29 09:51:20.217 INFO EDCORE (Main): Minidump created. dcs.20250729-095121.crash dcs.20250729-095121.dmp dcs.log.old

Guys, thanks a lot for your replies here. Sorry I totally missed your responses! All makes sense now. And also proves that I was not the only idiot not understanding how to identify the max radar gimbal limit in FC3 MiG-29. Which I think is still basically impossible. The diamond cue moving left and right on the HUD makes perfect sense in the real thing. Hopefully the FF MiG-29 has this modelled well. Can I ask one more thing, I've also had a read through the MiG-29 pilot manual but can't seem to find any reference of how to operate relative to Bullseye or "orientation point" as it would be called in Russian. Is there a way of referencing BE in the real MiG-29 somehow without using mental arithmetic and geometry based off a WP?

Yes, you did. https://forum.dcs.world/topic/78139-rakety-v-dcs/page/556/#findComment-5672192 Now it's all clear. Thanks. The delayed ignition of the second stage could prove to be a problem in combat though. It'd need constant target data input to calculate the impact time and use it optimally.

this is already reported, as soon as we have a fix ready it will be in a patch thanks

I fly VR and use MSAA 4x. I'd recommend MSAA nearly always over DLSS. Only when I do not need to be spotting a plane and maybe need additional FPS, I have a preset with DLSS. In all cases where you need to be spotting anything, MSAA is superior to DLSS in my opinion. ...and spotting dots to 2px.

Hi - i have looked at this, and I can replicate the shift only in the mission you attached. Are you able to replicate in a simple misison?

It's reported afaik, and that I think is wht problem with SPI, they had the same problem with previous pod.

Thank you, @SignorMagnifico! I'm able to reproduce the issue in your track as soon as I add Motion Blur, even after I take control over it (which is rarely the case with tracks showing the infamous flickering black screen). I tried your track with a different aircraft (F-16) and couldn't reproduce the bug anymore. I then made a new mission over Caucasus with dense fog and a sunset with two F-4En and... I made a strobe light out of DCS. Still no such issue with the F-16. I'll try some more aircraft before reporting it. EDIT: I'm now able to reproduce the issue without fog. I believe there are two issues: the F-4 induced motion blur issue (I'll report it), and the one described by @HR-Crumble that I'm yet to reproduce. F-4 induced issue reported.

Sorry literally just saw your reply. Yeah it sucks that we can't get the MiG-31 to behave more realistically! They should really hard-code it somehow to never engage in BFM since it would never do that in real life. But you're right, their list of priorities is pretty huge and I guess the MiG will be somewhere quite far down on the list