llOPPOTATOll

Ive had my game crash twice 2023-03-11 05:22:35.700 ERROR EDCORE (1696): More out of memory in ed_malloc for 4151120 bytes. 2023-03-11 05:22:35.700 INFO EDCORE (1696): try to write dump information 2023-03-11 05:22:35.707 INFO EDCORE (1696): # -------------- 20230311-052236 -------------- 2023-03-11 05:22:35.712 INFO EDCORE (1696): DCS/2.8.3.37556 (x86_64; MT; Windows NT 10.0.22621) 2023-03-11 05:22:35.717 INFO EDCORE (1696): F:\DCS World OpenBeta\bin-mt\edterrainGraphics41.dll 2023-03-11 05:22:35.720 ERROR DX11BACKEND (16552): failed to create index buffer. Reason: E_OUTOFMEMORY 2023-03-11 05:22:35.722 ERROR DX11BACKEND (16552): failed to create structed buffer. Reason: E_OUTOFMEMORY 2023-03-11 05:22:35.722 INFO EDCORE (1696): # C0000005 ACCESS_VIOLATION at 00007ff9996ada00 00:00000000 2023-03-11 05:22:35.722 ERROR DX11BACKEND (16552): CreateShaderResourceView FAILED. Reason: E_INVALIDARG 2023-03-11 05:22:35.722 ERROR DX11BACKEND (16552): failed to create index buffer. Reason: E_OUTOFMEMORY 2023-03-11 05:22:35.724 ERROR DX11BACKEND (16552): failed to create vertex buffer. Reason: E_OUTOFMEMORY 2023-03-11 05:22:35.724 ERROR DX11BACKEND (16552): Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:183 2023-03-11 05:22:35.724 ERROR EDCORE (15028): std exception: bad allocation 2023-03-11 05:22:35.727 INFO EDCORE (1696): SymInit: Symbol-SearchPath: 'F:\DCS World OpenBeta\bin-mt;', symOptions: 532, UserName: 'kayak' 2023-03-11 05:22:35.732 INFO EDCORE (1696): OS-Version: 10.0.22621 () 0x100-0x1 2023-03-11 05:22:35.734 ERROR DX11BACKEND (16552): failed to create vertex buffer. Reason: E_OUTOFMEMORY 2023-03-11 05:22:35.734 ERROR DX11BACKEND (16552): Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:183 2023-03-11 05:22:35.735 ERROR DX11BACKEND (16552): failed to create index buffer. Reason: E_OUTOFMEMORY 2023-03-11 05:22:35.737 INFO EDCORE (1696): 0x00000000000cda00 (edterrainGraphics41): createInstancerRenderable + 0x301E0 2023-03-11 05:22:35.737 ERROR DX11BACKEND (16552): failed to create index buffer. Reason: E_OUTOFMEMORY 2023-03-11 05:22:35.738 ERROR DX11BACKEND (16552): failed to create vertex buffer. Reason: E_OUTOFMEMORY 2023-03-11 05:22:35.738 ERROR DX11BACKEND (16552): Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:183 2023-03-11 05:22:35.738 ERROR DX11BACKEND (16552): failed to create index buffer. Reason: E_OUTOFMEMORY 2023-03-11 05:22:35.738 ERROR DX11BACKEND (16552): failed to create vertex buffer. Reason: E_OUTOFMEMORY 2023-03-11 05:22:35.738 ERROR DX11BACKEND (16552): Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:183 2023-03-11 05:22:35.738 ERROR DX11BACKEND (16552): failed to create index buffer. Reason: E_OUTOFMEMORY 2023-03-11 05:22:35.739 ERROR DX11BACKEND (16552): failed to create vertex buffer. Reason: E_OUTOFMEMORY 2023-03-11 05:22:35.739 ERROR DX11BACKEND (16552): Failed assert `false && "failed to create vertex buffer"` at Projects\render\dx11backend_win8\Source\DX11BufferManager.cpp:183 2023-03-11 05:22:35.739 ERROR DX11BACKEND (16552): failed to create index buffer. Reason: E_OUTOFMEMORY 2023-03-11 05:22:35.741 INFO EDCORE (1696): 0x00000000000cf7e3 (edterrainGraphics41): createInstancerRenderable + 0x31FC3 2023-03-11 05:22:35.741 INFO EDCORE (1696): 0x000000000025b82f (edterrain4): landscape5::Surface5File::verticalIntersection + 0x644F 2023-03-11 05:22:35.742 INFO EDCORE (1696): 0x0000000000259d7f (edterrain4): landscape5::Surface5File::verticalIntersection + 0x499F 2023-03-11 05:22:35.742 INFO EDCORE (1696): 0x0000000000256336 (edterrain4): landscape5::Surface5File::verticalIntersection + 0xF56 2023-03-11 05:22:35.742 INFO EDCORE (1696): 0x0000000000256361 (edterrain4): landscape5::Surface5File::verticalIntersection + 0xF81 2023-03-11 05:22:35.742 ERROR EDCORE (17420): More out of memory in ed_malloc for 7955184 bytes. 2023-03-11 05:22:35.742 INFO EDCORE (1696): 0x0000000000256361 (edterrain4): landscape5::Surface5File::verticalIntersection + 0xF81 2023-03-11 05:22:35.743 WARNING LOG (17864): 4 duplicate message(s) skipped. 2023-03-11 05:22:35.743 INFO EDCORE (1696): 0x000000000025aac1 (edterrain4): landscape5::Surface5File::verticalIntersection + 0x56E1 2023-03-11 05:22:35.804 INFO EDCORE (1696): 0x0000000000257df4 (edterrain4): landscape5::Surface5File::verticalIntersection + 0x2A14

Yes, but not implemented in dcs

There should be a way to designate jamming contacts and shoot on them in HOJ

The TSD doesnt show datalink. 98% of the L-16 stuff is on the SIT page (and yes, the only L-16 thing that appears on the AA RDR is 1 single DL track which you can choose on the SIT) which is like the strike eagle's SA page.

It’s very unlikely

Yes, I’m sure.

LRS isn’t a thing for our viper, but ULS (Uplook search) is

Smart weapons requires SMART PACS, which they said wont be there at early access

More likely, no

How does the system correlate a contact that you don’t know the range of? You have to use common sense for this, jamming and stuff like that is all classified. How does the jet correlate it to the datalink track 20nm away instead of the one 40nm away, how does the jet know? It doesn’t, so it shouldn’t correlate

M4.2+ Should also have 127. It was increased to 999 in M5

Look for the XXX>XXX The Xs to the left of the > indicate the range to the current steerpoint. The Xs to the right of the > indicates the current steerpoint. Say for the example of 30>003 you can think of it like theres 30nm -> stpt3 to remember which number is which

They shouldnt get instant launch warning even in STT

Also MPPRE is missing

Technically the F-16 sets the last mfd setup it had at shutdown so having it remember your mfd setup would be realistic.

Amazing job with the new manual, its very good. One suggestion for the next update to it, for the diagrams that are hyperlinked like the cockpit one, add like a hyper link back to the original image so you can easily return back to it. It would also be nice if it described the different steerpoint blocks.

The “modes” are the ECCM modes in the FCR CNTL page

How is this issue [correct as-is] [fixed] and [reported] all at the same time

Why is this a wishlist item? It is currently not working as it should, this is a bug/problem.

TFR would not work on our F-16, the TFR function was removed from all M4.2+ vipers

Start 1 should have a lower chance of working, so always use start 2.

Yes its realistic

The MIG-23 does not have a Mode 4 IFF transponder, so it should not replay at all. Mode 4 unknown symbology should be pretty rare to see. It means that there are valid mode 4 replies being received, but not enough to overcome the threshold for it to show a green circle.

BN is correct, you need to TMS Left long. However it should be possible to use NCTR without going to STT

So now its [missing actual evidence], so what is this "actual" evidence that you want? i've provided sufficient evidence of this.