Buzzer1977

Is Normandy Normandy or Normandy 2.0 ? And if Normandy is Normandy 2.0, where is Normandy? I'm confused. What would be the name for Normandy 2.0 to use with the installer?

Yep, it's now fixed. How are the names of the all the other maps, so i can check if they're correctly installed as well?

In the past DCS_updater from the dedicated server installation took care of this. How do i check which maps are installed on the dedicated server?

dedicated server won't host a mission on the Sinai map with F-15E 2023-06-23 17:06:09.394 INFO EDCORE (Main): (dDispatcher)enterToState_:3 2023-06-23 17:07:26.320 INFO WORLDGENERAL (Main): loading mission from: "C:\Users\heiko\Saved Games\DCS\Missions\Sinai-Serverbug.miz" 2023-06-23 17:07:32.256 WARNING LOG (9900): 1 duplicate message(s) skipped. 2023-06-23 17:07:32.256 INFO ASYNCNET (Main): server has started 2023-06-23 17:07:32.257 INFO ASYNCNET (Main): Using LEDBAT for UDP congestion control. 2023-06-23 17:07:32.264 ERROR ASYNCNET (Main): AddPortMapping(10308, 10308, 192.168.178.30, TCP) failed with code 403 (UnknownError) 2023-06-23 17:07:32.269 ERROR ASYNCNET (Main): GetSpecificPortMappingEntry(10308, TCP) failed with code 714 (NoSuchEntryInArray) 2023-06-23 17:07:32.284 ERROR ASYNCNET (Main): AddPortMapping(10308, 10308, 192.168.178.30, TCP) failed with code 403 (UnknownError) 2023-06-23 17:07:32.291 ERROR ASYNCNET (Main): GetSpecificPortMappingEntry(10308, TCP) failed with code 714 (NoSuchEntryInArray) 2023-06-23 17:07:32.291 ERROR ASYNCNET (Main): UPNP failed to map server port 10308 2023-06-23 17:07:32.337 ERROR ASYNCNET (Main): AddPortMapping(8088, 8088, 192.168.178.30, TCP) failed with code 403 (UnknownError) 2023-06-23 17:07:32.344 ERROR ASYNCNET (Main): GetSpecificPortMappingEntry(8088, TCP) failed with code 714 (NoSuchEntryInArray) 2023-06-23 17:07:32.396 ERROR ASYNCNET (Main): AddPortMapping(8088, 8088, 192.168.178.30, TCP) failed with code 403 (UnknownError) 2023-06-23 17:07:32.403 ERROR ASYNCNET (Main): GetSpecificPortMappingEntry(8088, TCP) failed with code 714 (NoSuchEntryInArray) 2023-06-23 17:07:32.403 ERROR ASYNCNET (Main): UPNP failed to map HTTP port 8088 2023-06-23 17:07:32.403 INFO ASYNCNET (Main): Successfully set up Dual-Stack socket, using both IPv4 and IPv6 2023-06-23 17:07:32.403 INFO ASYNCNET (Main): Listen to IPv6 on port 10308 2023-06-23 17:07:32.405 WARNING ASYNCNET (Main): removed unsupported mission file from the list: C:\Users\heiko\Saved Games\DCS\Missions\Sinai-Serverbug.miz 2023-06-23 17:07:32.469 INFO ASYNCNET (Main): server has stopped dcs.log Sinai-Serverbug.miz

Same here. 5950x, 128GB, RTX3090, HP Reverb G2

When ever DCS get's under load, my Reverb G2 blacks out. When playing larger missions, or playing for a longer time it get's dark for a few seconds. It's more likely to happen while playing when the G2 is in 90Hz and there is a lot going on in the mission. Likely the same effect comes to play in the mission editor when saving a larger mission. Each time you hit the save button, the Reverb goes blank. Because it's reproduceable in the mission editor when ever i hit the save button, i'd guess it's not a HW problem. HW: Ryzen 9 5950x, 128 GB DDR4, RTX3090, PCIe 4.0 SSDs ( 1 for OS, 1 for DCS ), HP Reverb G2 DxDiag.txt dcs.log

Had the same issue with the tomcat.

Not that i'm aware of.

Yep, seems like i've accidentally activated the history filter.

I created a mission with various AC, also with F-14A&B. But after some time working in the editor, i'm no longer able to add new F-14s. I can only copy the existing ones in the mission. ATQ.miz dcs.log

I was doing some mission editing, running in VR with MT. When leaving DCS, it got stuck with the following message in the log. (2023-04-08 10:11:52.576 INFO APP (Main): Command line: "G:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin-mt\DCS.exe" --force_enable_VR) 2023-04-08 14:25:19.724 INFO TERRAIN (Main): lSystem::exit() 2023-04-08 14:25:19.729 INFO TERRAIN (Main): lSystem::CleanScenes() 2023-04-08 14:25:34.287 INFO DXGUI_WIN_ADAPTER (Main): resize main window to [3840, 2160] 2023-04-08 14:25:34.292 WARNING SCENE (20196): Scene was removed with 4 alive objects 2023-04-08 14:25:34.292 WARNING SCENE (20196): Scene was removed with 1 alive lights 2023-04-08 14:25:34.297 WARNING SCENE (20196): Scene was removed with 4 alive objects 2023-04-08 14:25:37.048 INFO DX11BACKEND (20196): DX11Renderer::shutdown() 2023-04-08 14:25:37.105 INFO EDCORE (Main): try to write dump information 2023-04-08 14:25:37.187 INFO EDCORE (Main): # -------------- 20230408-142537 -------------- 2023-04-08 14:25:37.190 INFO EDCORE (Main): DCS/2.8.3.38090 (x86_64; MT; Windows NT 10.0.22621) 2023-04-08 14:25:37.193 INFO EDCORE (Main): G:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin-mt\Visualizer.dll 2023-04-08 14:25:37.196 INFO EDCORE (Main): # C0000005 ACCESS_VIOLATION at 00007ffbf2d06d80 00:00000000 2023-04-08 14:25:37.199 INFO EDCORE (Main): SymInit: Symbol-SearchPath: 'G:\Program Files (x86)\Steam\steamapps\common\DCSWorld\bin-mt;', symOptions: 532, UserName: 'heiko' 2023-04-08 14:25:37.202 INFO EDCORE (Main): OS-Version: 10.0.22621 () 0x100-0x1 2023-04-08 14:25:37.205 INFO EDCORE (Main): 0x0000000000086d80 (Visualizer): MouseCursorManager::clipCursor + 0x0 2023-04-08 14:25:37.208 INFO EDCORE (Main): 0x0000000000007826 (dxgui_win_adapter): gui::ApplicationWin::skipBoxMouseCursor + 0x36 2023-04-08 14:25:37.208 INFO EDCORE (Main): 0x0000000000004424 (dxgui_win_adapter): gui::ApplicationWin::dispatchMessage + 0x74 2023-04-08 14:25:37.208 INFO EDCORE (Main): 0x00000000000034d7 (dxgui_win_adapter): gui::ApplicationWin::~ApplicationWin + 0x6F7 2023-04-08 14:25:37.208 INFO EDCORE (Main): 0x0000000000018281 (USER32): DispatchMessageW + 0x741 2023-04-08 14:25:37.209 INFO EDCORE (Main): 0x0000000000017f3c (USER32): DispatchMessageW + 0x3FC 2023-04-08 14:25:37.209 INFO EDCORE (Main): 0x00000000000230bd (USER32): GetClassLongW + 0x58D 2023-04-08 14:25:37.209 INFO EDCORE (Main): 0x00000000000a2c94 (ntdll): KiUserCallbackDispatcher + 0x24 2023-04-08 14:25:37.209 INFO EDCORE (Main): 0x00000000000014d4 (win32u): NtUserPeekMessage + 0x14 2023-04-08 14:25:37.209 INFO EDCORE (Main): 0x0000000000021bdf (USER32): PeekMessageW + 0x1CF 2023-04-08 14:25:37.209 INFO EDCORE (Main): 0x0000000000021aac (USER32): PeekMessageW + 0x9C 2023-04-08 14:25:37.209 INFO EDCORE (Main): 0x0000000000097674 (gameoverlayrenderer64): OverlayHookD3D3 + 0x22B14 2023-04-08 14:25:37.209 INFO EDCORE (Main): 0x0000000000853414 (DCS): SW + 0x3BD064 2023-04-08 14:25:37.209 INFO EDCORE (Main): 0x0000000000105617 (Visualizer): smSceneManager::DestroySceneManager + 0xD7 2023-04-08 14:25:37.209 INFO EDCORE (Main): 0x000000000086e9c5 (DCS): SW + 0x3D8615 2023-04-08 14:25:37.209 INFO EDCORE (Main): 0x00000000023542f7 (DCS): AmdPowerXpressRequestHighPerformance + 0xFB02F3 2023-04-08 14:25:37.210 INFO EDCORE (Main): 0x0000000000c50292 (DCS): SW + 0x7B9EE2 2023-04-08 14:25:37.210 INFO EDCORE (Main): 0x00000000000126bd (KERNEL32): BaseThreadInitThunk + 0x1D dcs.log

Would be nice to have at least one Greek and one Portuguese livery

Refueling Tornado IDS 4 ship on KC-135MPRS only 1&2 refuel, 3&4 are stuck. Track, screenshot, debriefing and log added. TornadoKC135MPRSRefuel-Bug.trk dcs.log TornadoKC135MPRSRefuel-Bug.log

Under 2.7 definitely affected were MiG-21 (all Slovakian default livery), F-14(all Jolly Rogers), F/A-18(not all liveries), E-2, and some others i can't recall.

If you're on a AMD system on a x570 board make sure your BIOS runs at least AGESA 1.2.0.3 or higher. For the G2 make sure you're on the latest firmware (15 Rev.A) and have the new replacement cable ( P/N: L72080-002 SPS: M52188-001 )

Happened also under 2.7 but not to all aircraft and liveries. With 2.8 the number of aircraft and liveries affected that fall back to the default livery increased.

@Flappie You forgot to tag this thread as "reported earlier" so people will know it's already reported.

@Flappie Is ED aware of this issue? If so, could this thread get tagged? There are already other threads on the issue like in the AH64 bug section ... https://forum.dcs.world/topic/312158-game-very-slow-to-start-after-28/#comment-5082945

Didn't work for me. Even erased the entire saved games DCS folder without success.

Loading textures actually is a problem since 2.8

Could it be because i have the steam client version and the standalone DCS server version installed ?

Screenshot from the mission editor and the flight, the mission file, track file and dcs.log. I cleared the saved Games/DCS Folder except for 'config' before starting DCS. dcs.log F-5E-275Gal-Livery-Bug.trk Liverlies-Bug.miz

No mods.

I haven't installed any skins for the C-101. And in multiplayer where i usually play, skins are messed up in general. Update: I drilled it down. In my case it actually is a problem related to multiplayer server, because on multiplayer the C-101CC will show up with the default livery of the C-101EB which lacks pylons for A2A missiles.

Having the same issue. No pylons.