Harker

I just tested it and it doesn't seem weird to me. When it's coupled with the AWW-13, you can release whenever or when you're in range of the designation and then guide it. If you're dropping without the AWW-13, the seeker needs to be locked onto something first, like with the AGM-65F.

Our Hornet also has INS aided by GPS, called AINS. I imagine that these INS update options are used when GPS is completely unavailable or n only on-secure GPS connection is available and the NOSEC option is not desired.

That happens in DCS. IRL, the fighter-missile datalink remains after the missile goes active, so that helps. Also, the missile is provided with several criteria specific to the target, namely Doppler gate, range gate etc. All of these minimize the chance of going after the wrong target, although the possibility is always there, especially if the missile doesn't see its intended target and then throws the gates open, in order to increase its chances of picking something up. It's just that in DCS, it's worse than it should be, because all of the above target criteria is not simulated.

Are you implying that DCS is expensive and thus not a video game? The modules are priced just a little more than mainstream video games. Have you seen the prices for actual simulator software used to train people? Besides, DCS is advertised and marketed as a game, not as a training tool. ED made a good decision to emphasize that.

No one is trying to use this document for any meaningful purpose, this is a video game and all we can see at most is the front end of the system, not how it works in reality. ED doesn't need to know the latter either. DCS only shows how things look. Also, no one is publishing it, posting it or directly quoting it. I happen to work for a government agency that works with restricted documents a lot and I can tell you that this is practically the opposite of restricted, seeing as it's so easily available online. If the US DoD cared about it, that website that's accessible with a simple Google search, wouldn't have it available. As for the tag, it's clear from this document, as well as other, more open sources, that what we're talking about here is true and the MSI system has a lot of functionality that is currently not present in the DCS Hornet.

The curvature is a visual effect only. But yeah, I agree with you, the bright border under the clouds, that extends to infinity, looks very jarring. +1

The previous behavior was unrealistic. You now have to depress the TDC in MAN to defined a new scan center. If you are in AUTO with an L+S, it'll enter BIAS and move the scan center as much as possible, but keep the L+S in the scan. AUTO is still not working as well as it should, but this was a positive change. If you do want the scan to always follow the TDC, depress on empty space and hold for 1 sec and it'll go into SPOT mode, where a 22 degree scan will follow the cursor and remain azimuth stabilized. Works in RWS and TWS.

I'm not arguing that DCS loses its appeal to some people if they can't use VR (although monitors will definitely still be a thing for a long time, IMO), but the idea that people without VR should be thankful for the fact that they don't have VR is... weird, considering that VR is not forced upon you and you certainly own a monitor. It's like saying that people without cars should be thankful they don't have cars, because gas prices went up, whereas the option of public transport exists. Weird notion is all I'm saying. Again, I do agree with you that they should focus on fixing existing issues first or at least continue development in such a manner that will remedy such issues as soon as possible.

+1. That'd be very useful for missions where avoiding detection is critical.

I mean, I don't disagree with you, that they should fix the present issues before moving on, but "thankful" to be playing on a monitor? Everyone with VR can also play on a monitor, if they so choose.

Yep, the MIDS radios are hugely useful in MP. As for using the KY-58, you need to turn it to ON, place the MODE knob to C. It'll encrypt COMM2. Select the same encryption channel (1-6) as the others and you're good to go. I don't think the rest of the modes do anything in DCS/SRS.

He's not an employee of ED, he's just another player, who's helping you to submit a good bug report. It's not his job to test anything. And for that matter, neither is mine. Your description of the issue is unclear. Either attach a short track or make a video about it, so the developers can see exactly what you're experiencing. Otherwise, people can't look into it, because they don't know what to look for.

You need to salute in order to signal you're ready to launch. You can either set up a key bind in the controls or use the Ground Crew comms menu.

+1

@FlappieI haven't had any long play sessions since I deleted the DCS folder at AppData/Local/Temp/, but I've had some short ones and had zero crashes. Seems like the driver update to 466.27 and deleting the DCS temp folder worked. Fingers crossed. I'll probably have a long MP session in a few days, I'll update.

This is a case where macros are perfectly acceptable. Otherwise you need to spam the button like crazy. I also used to make CM programs for the F-15C back in the day, it was the only way to use CM effectively. IMO, it depends on whether or not the real aircraft has a switch that does all that. If someone doesn't have enough buttons on their setup, I'd say that it's perfectly acceptable to bind gear+flaps together. The trim is another issue, however, since trimming for landing is part of the pilot's workload and actually takes some practice (like in the F-14). Tangential, but that specific example of trimming for landing also cannot work without some sort of feedback from the game, because the trim setting depends on weight, speed etc, so a macro getting that info and using it to send appropriate presses to the trim keys would definitely be considered cheating. But we're not talking about that. If the macro instead just presses the trim key for 2 seconds though, I wouldn't classify it as cheating, more of a convenience thing. Same for the trigger, although again, kind of a useless macro here. It'd be cheating if it was an action like "trigger + change target + go STT + trigger" or whatever.

I just want to add that I've also noticed this issue on the Persian Gulf. It occurred with the ATFLIR in A/A mode, looking towards Dubai. No track at this time, but I'll make one when I get the chance.

Yeah, makes sense. I'll switch to the SSD.

Found it, that did it! It was on my secondary drive, an HDD I use for storage. I had directed program-related temp and such to be saved there, in Windows. I'll delete it and see if it helps. After the latest driver update, I'm not getting that any more, the driver hasn't crashed, yet. This only shows up with driver crashes and I suspect it occurs after the driver crash itself, since Precision is used to monitor the GPU clocks, control fan speeds etc. If I see that error again or if the driver crashes, I'll disable it and try again. Thanks a lot for the help, I appreciate it!

I still CTD, but it seems to have helped a bit with the DX11BACKEND errors

I stress-tested my components when the crashes started, they're all fine. All my other games play fine without any issues. The driver crashes only occured in DCS and started as soon as it updated to 2.7, so I'd say that the problem is isolated there. Actually, after updating to the 466.27 driver, I don't get this DXGI_ERROR_DEVICE_REMOVED anymore, but I still get DX11BACKEND errors. Specifically errors like that: 2021-04-30 21:21:20.695 ERROR_ONCE DX11BACKEND: render target 'cloudShadows' not found 2021-04-30 21:21:20.695 ERROR_ONCE DX11BACKEND: render target 'CascadeShadowMap' not found 2021-04-30 21:21:20.695 ERROR_ONCE DX11BACKEND: render target 'mainDepthBuffer_copy' not found 2021-04-30 21:21:20.695 ERROR_ONCE DX11BACKEND: render target 'DummyShadowMap' not found and 2021-04-30 21:06:53.693 ERROR_ONCE DX11BACKEND: texture 'lha_04_wm_map' not found. Asked from 'NGMODEL' 2021-04-30 21:06:53.763 ERROR_ONCE DX11BACKEND: texture 'lha_02_wm_map' not found. Asked from 'NGMODEL' 2021-04-30 21:06:53.827 ERROR_ONCE DX11BACKEND: texture 'lha_01_wm_map' not found. Asked from 'NGMODEL' 2021-04-30 21:06:53.992 ERROR_ONCE DX11BACKEND: texture 'lha_05_wm_map' not found. Asked from 'NGMODEL' Looks like the game is looking for assets it cannot locate. This was in a MP session, without any extra asset mods etc. The folders I created in User\AppData\Local\Temp\ are empty, I don't think they're used. And could you please let me know why SSLR would be a problem? I was using it prior to 2.7 without issues. I'll disable it and test anyway, just asking. Thank you!

Nope, still crashing, with the Nvidia 466.27 driver as well. Still DX11 BACKEND errors...

Yes, "offboard" is for non-ownship tracks in the context of MSI, but I was just speaking from the radar's perspective, that it can be commanded to search for a contact it has not detected itself. I could've used another term, but I was merely referring to that particular feature. As far as the radar is concerned, as an isolated entity, any track not created by itself is the same. So if the one thing is possible, the other should be as well. But a picture is worth a thousands words and the picture you posted from this really nice series speaks for itself and settles the matter. Nice find!

Merci, Flappie, I created them. I'll play around a bit, see if this helps and report back.

Getting frequent crashes for no reason. It's often related to DX11BACKEND errors and it crashes the NVIDIA driver. I do not understand why, my GPU is not crashing with anything else. It wasn't even stressed, it was sitting at ~60% utilization. This problem started with 2.7 and is present in both the previous patch and this one. This is the error message I get most often. 2021-04-29 21:00:15.600 ERROR SOUND: can't load wave: "speech\eng\common\atc_navy_marshal\digits\point-continue" 2021-04-29 21:04:10.801 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-04-29 21:04:10.801 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:416 2021-04-29 21:04:10.801 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-04-29 21:04:10.801 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:416 2021-04-29 21:04:10.804 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-04-29 21:04:10.804 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:416 2021-04-29 21:04:10.804 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-04-29 21:04:10.804 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:416 2021-04-29 21:04:10.808 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-04-29 21:04:10.808 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:416 2021-04-29 21:04:10.808 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-04-29 21:04:10.809 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:416 2021-04-29 21:04:10.809 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-04-29 21:04:10.809 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:416 2021-04-29 21:04:10.809 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-04-29 21:04:10.809 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:416 2021-04-29 21:04:10.809 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-04-29 21:04:10.809 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:416 2021-04-29 21:04:10.809 ERROR DX11BACKEND: failed to create vertex buffer. Reason: DXGI_ERROR_DEVICE_REMOVED 2021-04-29 21:04:10.809 ERROR DX11BACKEND: Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:416 2021-04-29 21:04:10.849 ERROR DX11BACKEND: DX device removed. Reason: 0x887A0006 2021-04-29 21:04:11.523 WARNING LOG: 69 duplicate message(s) skipped. 2021-04-29 21:04:11.523 INFO EDCORE: try to write dump information At the same time, I get this application error in the Event Viewer. Faulting application name: DCS.exe, version: 2.7.0.5118, time stamp: 0x60812393 Faulting module name: PXSHW10_x64.dll, version: 0.3.6.0, time stamp: 0x5c0773f8 Exception code: 0xc0000005 Fault offset: 0x0000000000004b82 Faulting process id: 0x3418 Faulting application start time: 0x01d73d289d0326de Faulting application path: C:\Program Files\Eagle Dynamics\DCS World\bin\DCS.exe Faulting module path: C:\Program Files\EVGA\Precision X1\PXSHW10_x64.dll Report Id: 05726090-e11f-4a70-ac45-6579b1bf7916 Faulting package full name: Faulting package-relative application ID: I'll try the fix suggested by Flappie and report back. I don't have either of these folders. Should I? %USERPROFILE%/AppData/Local/Temp/DCS.openbeta %USERPROFILE%/AppData/Local/Temp/DCS