-
Posts
15314 -
Joined
-
Last visited
-
Days Won
9
Content Type
Profiles
Forums
Events
Posts posted by Flappie
-
-
Thanks to your video, I'm now sure we're seeing the same thing. We simply interpret it differently.
In your video, you place the edge of the rectangle next to the yellow line, but the anchor is not placed at the tip of the rectangle, it's the white square inside the rectangle, as seen here:
-
28 minutes ago, Elphaba said:
Would it help if I put a video on YouTube and created a new bug report or are you happy for me to add to this one, if what I'm reporting is different from the OP?
You chose wisely. I'll answer in the new thread.
- 1
-
I've seen this behaviour before for one user. I need to find the thread.
EDIT: here.
The user solved this issue by... buying a new PC.
- 1
-
From your first log:
2024-04-25 23:35:03.960 INFO WORLDGENERAL (Main): loaded from mission Scripts/World/birds.lua 2024-04-25 23:35:04.042 INFO LUA (Main): Lua: States: 705, CPU load: 4.0%, Mem: 472.9 MB 2024-04-25 23:35:04.371 ERROR ED_SOUND (21692): can't load wave: "effects\aircrafts\engines\mi8reductor" 2024-04-25 23:35:04.422 WARNING BACKENDCOMMON (22740): Need to reprocess [DDS] image '/textures/AH-64D_inside_D_Normal.dds' 2024-04-25 23:35:04.910 WARNING BACKENDCOMMON (6860): Need to reprocess [DDS] image '/textures/ah64_pilot_seat_all_Normal.dds' 2024-04-25 23:35:05.496 INFO TACVIEW.DLL (Main): Recording flight data in [E:\Jim\Documents\Tacview\Tacview-20240425-183505-DCS-AH64-IA-Sinai-Weapons_Practice.zip.acmi] 2024-04-25 23:35:05.497 WARNING BACKENDCOMMON (13636): Need to reprocess [DDS] image '/textures/AH-64D_inside_D_Normal.dds' 2024-04-25 23:35:05.499 INFO TACVIEW.DLL (Main): Export rights granted by the host: PlayerPlane=[1] PlayerSensors=[1] OtherObjects=[1] 2024-04-25 23:35:06.153 WARNING BACKENDCOMMON (13716): Need to reprocess [DDS] image '/textures/ah64_pilot_seat_all_Normal.dds' 2024-04-25 23:35:06.208 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2024-04-25 23:37:03.319 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2024-04-25 23:37:03.438 ERROR DX11BACKEND (17852): Can't map structured buffer. 2024-04-25 23:37:03.438 ERROR DX11BACKEND (17852): Failed assert `0` at Projects\render\dx11backend_win8\Source\DX11StructuredBuffer.cpp:100 2024-04-25 23:37:03.442 ERROR DX11BACKEND (17852): DX device removed. Reason: 0x887A0007 2024-04-25 23:37:03.445 ERROR DX11BACKEND (17852): Can't map structured buffer. 2024-04-25 23:37:03.445 ERROR DX11BACKEND (17852): Failed assert `0` at Projects\render\dx11backend_win8\Source\DX11StructuredBuffer.cpp:100 2024-04-25 23:37:03.448 ERROR DX11BACKEND (17852): DX device removed. Reason: 0x887A0007 2024-04-25 23:37:03.483 ERROR DX11BACKEND (17852): Can't map structured buffer. 2024-04-25 23:37:03.483 ERROR DX11BACKEND (17852): Failed assert `0` at Projects\render\dx11backend_win8\Source\DX11StructuredBuffer.cpp:100 2024-04-25 23:37:03.487 ERROR DX11BACKEND (17852): DX device removed. Reason: 0x887A0007 2024-04-25 23:37:03.568 WARNING WORLD (Main): ModelTimeQuantizer: ANTIFREEZE ENABLED 2024-04-25 23:37:03.570 WARNING WORLD (Main): ModelTimeQuantizer: SAME MODEL TIME 2024-04-25 23:37:03.572 ERROR DX11BACKEND (17852): Can't map structured buffer. 2024-04-25 23:37:03.572 ERROR DX11BACKEND (17852): Failed assert `0` at Projects\render\dx11backend_win8\Source\DX11StructuredBuffer.cpp:100 2024-04-25 23:37:03.575 INFO LUA (Main): Lua: States: 705, CPU load: 0.8%, Mem: 477.3 MB 2024-04-25 23:37:03.575 ERROR DX11BACKEND (17852): DX device removed. Reason: 0x887A0007 2024-04-25 23:37:03.577 ERROR DX11BACKEND (17852): Can't map structured buffer. 2024-04-25 23:37:03.577 ERROR DX11BACKEND (17852): Failed assert `0` at Projects\render\dx11backend_win8\Source\DX11StructuredBuffer.cpp:100 2024-04-25 23:37:03.581 ERROR DX11BACKEND (17852): DX device removed. Reason: 0x887A0007 2024-04-25 23:37:03.583 ERROR DX11BACKEND (17852): Can't map structured buffer. 2024-04-25 23:37:03.583 ERROR DX11BACKEND (17852): Failed assert `0` at Projects\render\dx11backend_win8\Source\DX11StructuredBuffer.cpp:100 2024-04-25 23:37:03.586 ERROR DX11BACKEND (17852): DX device removed. Reason: 0x887A0007 2024-04-25 23:37:03.589 ERROR DX11BACKEND (17852): Can't map structured buffer. 2024-04-25 23:37:03.589 ERROR DX11BACKEND (17852): Failed assert `0` at Projects\render\dx11backend_win8\Source\DX11StructuredBuffer.cpp:100 2024-04-25 23:37:03.593 ERROR DX11BACKEND (17852): DX device removed. Reason: 0x887A0007 2024-04-25 23:37:03.595 ERROR DX11BACKEND (17852): Can't map structured buffer. 2024-04-25 23:37:03.595 ERROR DX11BACKEND (17852): Failed assert `0` at Projects\render\dx11backend_win8\Source\DX11StructuredBuffer.cpp:100 2024-04-25 23:37:03.599 ERROR DX11BACKEND (17852): DX device removed. Reason: 0x887A0007 2024-04-25 23:37:03.601 ERROR DX11BACKEND (17852): Can't map structured buffer.
Your GPU struggles to handle textures. I think it can be caused by a corrupted game file issue or a GPU issue.
Try a DCS cleanup and repair. Choose the "slow" way.
-
HI. It seems the sim is unable to compile a crucial shader, which leads to the crash:
2024-04-26 01:56:37.432 INFO M2KC_FM (Main): M53P2 End of model preinit 2024-04-26 01:56:37.439 ERROR DX11BACKEND (7384): Shader "enlight/raycursor.fx:DIRECTX11=true;USE_DCS_DEFERRED=1;" failed to create. 2024-04-26 01:56:37.441 INFO EDCORE (7384): try to write dump information 2024-04-26 01:56:37.505 INFO EDCORE (7384): # -------------- 20240426-015638 -------------- 2024-04-26 01:56:37.539 INFO EDCORE (7384): DCS/2.9.4.53707 (x86_64; MT; Windows NT 10.0.19045) 2024-04-26 01:56:37.572 INFO EDCORE (7384): E:\Libraries\Other Games\DCS World OpenBeta\bin-mt\enlight.dll 2024-04-26 01:56:37.605 INFO EDCORE (7384): # C0000005 ACCESS_VIOLATION at 00007ffcbc7358eb 00:00000000 2024-04-26 01:56:37.638 INFO EDCORE (7384): SymInit: Symbol-SearchPath: '.', symOptions: 532, UserName: 'benre' 2024-04-26 01:56:37.672 INFO EDCORE (7384): OS-Version: 10.0.19045 () 0x300-0x1 2024-04-26 01:56:37.705 INFO EDCORE (7384): 0x00000000000658eb (enlight): enlight::RayCursor::build + 0x23B 2024-04-26 01:56:37.739 INFO EDCORE (7384): 0x00000000001f020a (CockpitBase): cockpit::ccMouseHandler::mouseButtonCommand_ + 0x2BA 2024-04-26 01:56:37.772 INFO EDCORE (7384): 0x00000000003613eb (CockpitBase): cockpit::MultiThreading::release_orphans + 0x53B 2024-04-26 01:56:37.805 INFO EDCORE (7384): 0x0000000000151232 (Visualizer): smSceneManager::DestroySceneManager + 0x8E2 2024-04-26 01:56:37.808 INFO EDCORE (7384): 0x00000000000277fd (SceneRenderer): DCSSceneRenderer::updateAuxViewport + 0x9CAD 2024-04-26 01:56:37.809 INFO EDCORE (7384): 0x00000000000542af (GraphicsCore): render::BaseRenderingPass::execute + 0x1F 2024-04-26 01:56:37.810 INFO EDCORE (7384): 0x0000000000054974 (GraphicsCore): render::BaseRenderingPass::execute + 0x6E4 2024-04-26 01:56:37.811 INFO EDCORE (7384): 0x0000000000058f7d (GraphicsCore): render::RenderGraph::render + 0xED 2024-04-26 01:56:37.811 INFO EDCORE (7384): 0x000000000001bbd2 (SceneRenderer): DCSSceneRenderer::renderBakedRenderGraph + 0x42 2024-04-26 01:56:37.812 INFO EDCORE (7384): 0x000000000016356a (Visualizer): smSceneManager::regLua + 0x137A 2024-04-26 01:56:37.813 INFO EDCORE (7384): 0x000000000014e974 (Visualizer): smCamera_Implement::getClipRegion + 0x19CB4 2024-04-26 01:56:37.814 INFO EDCORE (7384): 0x000000000013a08c (Visualizer): smCamera_Implement::getClipRegion + 0x53CC 2024-04-26 01:56:37.814 INFO EDCORE (7384): 0x0000000000151b72 (Visualizer): smSceneManager::DestroySceneManager + 0x1222 2024-04-26 01:56:37.815 INFO EDCORE (7384): 0x00000000000339c1 (edCore): ed::thread::_get_current_thread_id + 0x71 2024-04-26 01:56:37.816 INFO EDCORE (7384): 0x0000000000021bb2 (ucrtbase): _configthreadlocale + 0x92 2024-04-26 01:56:37.817 INFO EDCORE (7384): 0x0000000000017344 (KERNEL32): BaseThreadInitThunk + 0x14 2024-04-26 01:56:38.074 INFO EDCORE (7384): Minidump created.
Purge your "fxo" and "metashaders2" subfolders (they are located in your "Saved Games/DCS..." folder).
If this does not help, try a DCS cleanup and repair.
Still no joy? Uninstall then reinstall your GPU driver.
-
HI @Elphaba. Devs answered me. This is not a bug: add a flag name in the FLAG field so this flag gets updated anytime the player passes a waypoint (e.g. the flag will equal 5 when WP5 is passed).
You've been heard nonetheless: devs will soon* allow you to hide helper gates by leaving the FLAG field empty.
*no dates.
- 1
-
Just now, SMH said:
Sorry, tried searching the board for "cows die" and didn't find anything.
It's OK, sometimes bugs are first reported internally, which means you won't find anything on the forums.
1 minute ago, SMH said:How do features get undone like this?
I think @Nevyn may be onto something.
- 2
-
These are two different things. I believe OP asked for a fixed size.
I checked what you describe: from my point of view, there is no such thing as floating textboxes. Their position is fixed. The problem is that they are left-aligned: the anchor is at the bottom left of the rectangle (white square in the screenshot below). I think you are asking for a centered anchor. Is that it?
-
I don't have your issue. Can you reproduce the error with my mission? If not, please attach your .miz.
-
This was reported two years ago.
- 1
-
Thanks. The shadows issue is now reported.
-
-
Issue reproduced and reported.
Thanks for the heads up.
-
It may be, yes. I can't say for sure. You can first try a bigger pagefile, since it costs nothing.
- 1
-
6 minutes ago, AeriaGloria said:
Awesome graphic for showing how the gyros are toppled!
I feel inspired tonight.
- 2
-
21 minutes ago, whataboutbob71 said:
I'm telling him to target ahead where the sight is pointing and he is still off the screen trying to lock something else.
Precisely, because he cannot turn his sight to where the AI helper points anymore. Because the gyro is borked.
As you can see, when the gyro is borked, there's an offset between the AI helper logo and the periscope view. As a consequence, when you say "look over here (cross on the orange disc), Petrovitch will look over there (cross on the blue disc).
If you want to make sure of this, switch to the CPG position, look into the periscope and try to find your target. You wont be able to center the periscope on the target.
Solution : ask Petrovich to go Observ. off before you make your turns. This way, your gyro will stay aligned.
-
If you want us to help you with that, we'd need the latest zip file from your "Saved Games/DCS.../Logs" folder.
-
On 4/22/2024 at 10:19 PM, Flia said:
I didn't know that alt tabbing can somehow cause problems in DCS.
No, it doesn't. I asked because I wanted to be sure Alt+Tabbing was from your initiative, not from some program. Another user is seeing fast Alt+Tabbing in DCS and he does not know what causes them (and I have no idea either).
Pleas ensure your Windows power plan is not set to an eco mode. Choose normal or high/ultimate power plan and see if things improve.
-
This guide will help you: https://mcci.com/support/guides/how-to-change-the-windows-pagefile-size/
In your case, I recommend these values:
- Init size: 32768 (32GB)
- Max size: 32768 (32GB)
Windows uses a pagefile in order to relieve the system fast memory (RAM). The more RAM a PC has, the less page fle it needs. Your PC has 16GB of RAM, and DCS can very greedy when it comes to memory. A bigger pagefile might help, as long as the drive hosting the pagefile is fast.
- 1
-
Ok. Ensure your Windows power plan is not set to an economic mode.
-
Thanks for the heads up.
- The issue is clearly visible in the Yak-52 and the I-16 (2-blade), as well as in the Bf-109 and the Fw190 (3-blade).
- I could not spot the issue in the Spitfire, the P-51 and the P-47 (4-blade).
- Strangely, I could not spot the issue with the Mi-24 either (5-blade), nor with the Huey (2-blade). Maybe helicopter blades are simulated differently.
Issue reported.
- 2
-
Let's use videos taken from the deck, because as @Micr0 underlined, photographers "cheat" with longer exposure. Videos don't cheat as much.
Here's some footage from CVN-69 and CVN-70 (Nimitz class):
CVN-78 here (Ford class):
Back to the Nimitz class with CVN-72:
According to these videos, this photo does not cheat:
Here's a last one from CVN-76 (Nimitz class), with what looks like a longer exposition, but it's very useful to locate the spotlights:
null
A few observations:
- In most videos, the lower part of the island appears to be lit in yellow. This light comes from spotlights pointing downward. These spotlights are never lit in DCS.
- In all videos, the middle part of the island stays dark (they don't seem to use the top yellow lights very often). In DCS, the blue/teal lights are always turned off, while the top yellow lights are always turned on.
- In the last video, many lights are off. I assume it's a wartime configuration. In DCS, there's no such thing.
- 3
- 1
-
The next time it happens, please record the track when you exit the mission, then attach it here.
-
Glad you solved your problem!
- 1
Crash to Black Screen
in Game Crash
Posted
I believe you won't get the cleanup part, just the repair.