Hi, make sure you only run the UDBOLauncher and not dbo.exeIt seems like the game do a lot of duplicate ID which cause the crash but the real is why, because i delete the game, change the location of the folder, everything but its still crash.
i did as instructed but the crash still occur, duplicated ID and CStaticBox_Generic::GetStartPosY = FontSize StaticBoxSize Over. On the dbologHi, make sure you only run the UDBOLauncher and not dbo.exe
Likewise try a clean install with those specific steps:
0- Restart your computer
1- Unistall the game, delete the .zip folder
2- Download again and extract the folder inside the C:/Program Files/UltimateDBO folder3
- Open the Update.exe as administrator
4- Go to options and select Full Screen Mode with your screen resolution
5- Disable the HD Graphics options if they are enabled
6- Open the game
That error is benign, are you crashing when trying to login or while playing the game? Are you using UDBOLaunche or DBO exe?i did as instructed but the crash still occur, duplicated ID and CStaticBox_Generic::GetStartPosY = FontSize StaticBoxSize Over. On the dbolog
That error is benign, are you crashing when trying to login or while playing the game? Are you using UDBOLaunche or DBO exe?
CNtlPacketLockManager::IndividualUnlock (653) : [ASSERT] This packet isn't lock yet
[2025/12/29 Mon 22:31:20 PM] CNtlWorldSectorInfo::SectorShadowLoadFromFile (2524) : [ASSERT] Texture load failed.
Can you check if you've already got everything from the InstallThis zip by simply running each of them?this time the log add this
Can you check if you've already got everything from the InstallThis zip by simply running each of them?
Where is your folder located exactly? Try and whitelist it in windows defender in case something is interfering with the files, and use the repair files option in the launcher. Ensure any additional options from the launcher's settings are off and that windowed mode is enabled.
If you still get frequent crashes despite all of this being true, then something unknown must be going on, and we'll only be able to figure that out after I apply a patch that implements a crash error catcher.