Wont play?

[wodin]

OK suddenly decided it wont boot up. Just keeps going back to the launcher page.

[PipFromSlitherine]

What does the error log say?

Cheers

Pip

[wodin]

Not even getting an error log. Just click Play Game it will flash and then just stay on launcher. Tried reinstalling, to no avail. Tried with anti virus off..again no go.

Wasn't happening earlier when I started the game up but had no launcher page. Since getting the launcher page it's a no go.

[PipFromSlitherine]

So the log is empty? In Documents/My Games/CloseCombatTheBloodyFirst/error.log

How did you "get the launcher page"? The release game will open the launcher by default, so not sure how you were playing without it.

Cheers

Pip

[wodin]

20191003_190422
VER:900 : 10000
PLATFORM: WINDOWS
PLATFORM: STEAM
WinVer:10.0.18362.329
0: Radeon (TM) RX 480 Graphics
CPU String: AuthenticAMD
Stepping ID = 1
Model = 1
Family = 15
Extended family = 8
CLFLUSH cache line size = 64
APIC Physical ID = 2
CPU Brand String: AMD Ryzen 5 1600 Six-Core Processor
Cache Size = 512K
UNKNOWN TAGS IN: CONFIG/SYSTEM.TXT
Unknown Tag: MOVIEMODE
Unknown Tag: DYNAMICENV
Unknown Tag: LAYOUTKILLSENEMYX,
END: CONFIG/SYSTEM.TXT
Found DirectX Version Number: 4.09.00.0904
Creating Device.....
MonkeyInitStart
MIS: Found DD
MIS: IsHW
MIS: SetCoop
MIS: Setting Disp Mode
MIS: Done Init 3D Device
MIS: Tex Enum
MIS: SDRS
MIS: Init Decal Render
TS: Start
TS: IAPSent
TS: UILoaded
INITIAL LOAD 3168
TS: CC Engine Loaded
TS: BattleObj
TS: Managers
TS: BFBB
TS: LT
TS: InitDLUI
TS: Messages
TS: Ended
WARNING: Invalid main force unit in file T_BOOT_CAMP_TUTORIAL_TITLE.
WARNING: Invalid main force unit in file T_BOOT_CAMP_TUTORIAL_TITLE.
Starting map: Point290
00:00 BATTLE AI: BATTLE STANCE Defend (0)
00:00 BATTLE AI: BATTLE STANCE Probing Attack (1)
Playing as: 0
KERNEL MEMORY CHECKING IS **OFF**


THIS IS OLDER ERROR LOG SO NOT RELEVANT.

[wodin]

Looking at the error log text doc creation this doesn't seem to be the issue though.

[wodin]

Just checked. It doesn't create a new error txt doc. Like it never really even starts to load game. Just click Play and the launcher quickly falshes and then nothing..as if Play wasn't pressed.

[PipFromSlitherine]

If the error log isn't even being started then the issue is not with the game EXE, it likely isn't even being started. What happens if you try and run from the game EXE itself?

I guess the question is - what changed to both have a launcher suddenly appear and for the game to not be run by it?

Cheers

Pip

[wodin]

ORIGINAL: PipFromSlitherine

So the log is empty? In Documents/My Games/CloseCombatTheBloodyFirst/error.log

How did you "get the launcher page"? The release game will open the launcher by default, so not sure how you were playing without it.

Cheers

Pip

Got a key and when I first booted game up there was no front end launcher page at first. Just went straight into game.

[Denes]

"Check for Update" doesn't work
The answer: "Error".
But why ??

[wodin]

Well just wont start anymore. Tried reinstalling, rebooting PC, everything.

Oh hum.

[VPaulus]

So you don't have a launcher menu?

[wodin]

Yes but that's it just the launcher menu. I click play game and the menu does a quick blink and then nothing happens just stays on launcher menu. I can keep on clicking Play Game and nothing.

[wodin]

Still trying.

Just noticed this text file in Steam folder...

Fri Oct 04 11:07:20 2019 UTC - Module file name: H:\Steam\gameoverlayrenderer.dll
Fri Oct 04 11:07:20 2019 UTC - GameID = 811880
Fri Oct 04 11:07:20 2019 UTC - System page size: 4096
Fri Oct 04 11:07:20 2019 UTC - Hooking SetCursorPos, GetCursorPos, ShowCursor, and SetCursor
Fri Oct 04 11:07:20 2019 UTC - Modules at GameOverlayRenderer.dll attach
Fri Oct 04 11:07:20 2019 UTC - 01: autorun.exe - (00400000 to 00AD1000)
Fri Oct 04 11:07:20 2019 UTC - 02: ntdll.dll - (77280000 to 7741A000)
Fri Oct 04 11:07:20 2019 UTC - 03: KERNEL32.DLL - (75220000 to 75300000)
Fri Oct 04 11:07:20 2019 UTC - 04: aswhook.dll - (72C50000 to 72C60000)
Fri Oct 04 11:07:20 2019 UTC - 05: KERNELBASE.dll - (75560000 to 7575C000)
Fri Oct 04 11:07:20 2019 UTC - 06: apphelp.dll - (6EDE0000 to 6EE7F000)
Fri Oct 04 11:07:20 2019 UTC - 07: AcLayers.DLL - (6EAA0000 to 6ED24000)
Fri Oct 04 11:07:20 2019 UTC - 08: msvcrt.dll - (76010000 to 760CF000)
Fri Oct 04 11:07:20 2019 UTC - 09: USER32.dll - (75080000 to 75215000)
Fri Oct 04 11:07:20 2019 UTC - 10: win32u.dll - (760D0000 to 760E7000)
Fri Oct 04 11:07:20 2019 UTC - 11: GDI32.dll - (77240000 to 77261000)
Fri Oct 04 11:07:20 2019 UTC - 12: gdi32full.dll - (76800000 to 7695A000)
Fri Oct 04 11:07:20 2019 UTC - 13: msvcp_win.dll - (77110000 to 7718C000)
Fri Oct 04 11:07:20 2019 UTC - 14: ucrtbase.dll - (75930000 to 75A4F000)
Fri Oct 04 11:07:20 2019 UTC - 15: SHELL32.dll - (75A90000 to 7600A000)
Fri Oct 04 11:07:20 2019 UTC - 16: cfgmgr32.dll - (75A50000 to 75A8B000)
Fri Oct 04 11:07:20 2019 UTC - 17: shcore.dll - (76120000 to 761A4000)
Fri Oct 04 11:07:20 2019 UTC - 18: RPCRT4.dll - (763C0000 to 7647B000)
Fri Oct 04 11:07:20 2019 UTC - 19: SspiCli.dll - (74A50000 to 74A70000)
Fri Oct 04 11:07:20 2019 UTC - 20: CRYPTBASE.dll - (74A40000 to 74A4A000)
Fri Oct 04 11:07:20 2019 UTC - 21: bcryptPrimitives.dll - (767A0000 to 767FF000)
Fri Oct 04 11:07:20 2019 UTC - 22: sechost.dll - (75390000 to 75406000)
Fri Oct 04 11:07:20 2019 UTC - 23: combase.dll - (76520000 to 76796000)
Fri Oct 04 11:07:20 2019 UTC - 24: windows.storage.dll - (76AB0000 to 77075000)
Fri Oct 04 11:07:20 2019 UTC - 25: advapi32.dll - (75310000 to 75389000)
Fri Oct 04 11:07:20 2019 UTC - 26: profapi.dll - (75060000 to 75077000)
Fri Oct 04 11:07:20 2019 UTC - 27: powrprof.dll - (76A60000 to 76AA3000)
Fri Oct 04 11:07:20 2019 UTC - 28: UMPDC.dll - (76110000 to 7611D000)
Fri Oct 04 11:07:20 2019 UTC - 29: shlwapi.dll - (75510000 to 75554000)
Fri Oct 04 11:07:20 2019 UTC - 30: kernel.appcore.dll - (74FF0000 to 74FFF000)
Fri Oct 04 11:07:20 2019 UTC - 31: cryptsp.dll - (76960000 to 76973000)
Fri Oct 04 11:07:20 2019 UTC - 32: OLEAUT32.dll - (76480000 to 76512000)
Fri Oct 04 11:07:20 2019 UTC - 33: SETUPAPI.dll - (74BA0000 to 74FE9000)
Fri Oct 04 11:07:20 2019 UTC - 34: bcrypt.dll - (77220000 to 77239000)
Fri Oct 04 11:07:20 2019 UTC - 35: MPR.dll - (6EDC0000 to 6EDD8000)
Fri Oct 04 11:07:20 2019 UTC - 36: sfc.dll - (66680000 to 66683000)
Fri Oct 04 11:07:20 2019 UTC - 37: WINSPOOL.DRV - (74900000 to 7496B000)
Fri Oct 04 11:07:20 2019 UTC - 38: PROPSYS.dll - (74770000 to 74835000)
Fri Oct 04 11:07:20 2019 UTC - 39: IPHLPAPI.DLL - (74730000 to 74762000)
Fri Oct 04 11:07:20 2019 UTC - 40: sfc_os.DLL - (6EDB0000 to 6EDBF000)
Fri Oct 04 11:07:20 2019 UTC - 41: IMM32.DLL - (76980000 to 769A5000)
Fri Oct 04 11:07:20 2019 UTC - 42: COMDLG32.dll - (769B0000 to 76A60000)
Fri Oct 04 11:07:20 2019 UTC - 43: ole32.dll - (75410000 to 75507000)
Fri Oct 04 11:07:20 2019 UTC - 44: imagehlp.dll - (760F0000 to 7610B000)
Fri Oct 04 11:07:20 2019 UTC - 45: lua5.1.dll - (6EA40000 to 6EA94000)
Fri Oct 04 11:07:20 2019 UTC - 46: WINMM.dll - (749E0000 to 74A04000)
Fri Oct 04 11:07:20 2019 UTC - 47: WSOCK32.dll - (74510000 to 74518000)
Fri Oct 04 11:07:20 2019 UTC - 48: WS2_32.dll - (74AD0000 to 74B2E000)
Fri Oct 04 11:07:20 2019 UTC - 49: VERSION.dll - (74980000 to 74988000)
Fri Oct 04 11:07:20 2019 UTC - 50: MSACM32.dll - (6A5F0000 to 6A609000)
Fri Oct 04 11:07:20 2019 UTC - 51: MSIMG32.dll - (74970000 to 74976000)
Fri Oct 04 11:07:20 2019 UTC - 52: COMCTL32.dll - (74520000 to 7472F000)
Fri Oct 04 11:07:20 2019 UTC - 53: oledlg.dll - (72E80000 to 72EAC000)
Fri Oct 04 11:07:20 2019 UTC - 54: urlmon.dll - (70F90000 to 7113B000)
Fri Oct 04 11:07:20 2019 UTC - 55: gdiplus.dll - (740D0000 to 74239000)
Fri Oct 04 11:07:20 2019 UTC - 56: NETAPI32.dll - (744E0000 to 744F3000)
Fri Oct 04 11:07:20 2019 UTC - 57: WINMMBASE.dll - (749B0000 to 749D3000)
Fri Oct 04 11:07:20 2019 UTC - 58: iertutil.dll - (71140000 to 71369000)
Fri Oct 04 11:07:20 2019 UTC - 59: gameoverlayrenderer.dll - (69AC0000 to 69C27000)
Fri Oct 04 11:07:20 2019 UTC - 60: PSAPI.DLL - (74B90000 to 74B96000)
Fri Oct 04 11:07:20 2019 UTC - ----------------------------
Fri Oct 04 11:07:20 2019 UTC - Initializing Audio...
Fri Oct 04 11:07:20 2019 UTC - IAudioClient_Initialize - SUCCEEDED
Fri Oct 04 11:07:20 2019 UTC - Audio client initialized: 0x00E5FE28
Fri Oct 04 11:07:20 2019 UTC - Device:
Fri Oct 04 11:07:20 2019 UTC - Audio client mix format:
Fri Oct 04 11:07:20 2019 UTC - format: 65534
Fri Oct 04 11:07:20 2019 UTC - channels: 2
Fri Oct 04 11:07:20 2019 UTC - samples/sec: 192000
Fri Oct 04 11:07:20 2019 UTC - bytes/sec: 1536000
Fri Oct 04 11:07:20 2019 UTC - alignment: 8
Fri Oct 04 11:07:20 2019 UTC - bits/sample: 32
Fri Oct 04 11:07:20 2019 UTC - channel mask: 0x3
Fri Oct 04 11:07:20 2019 UTC - data format: {00000003-0000-0010-8000-00AA00389B71}
Fri Oct 04 11:07:20 2019 UTC - Audio hooked
Fri Oct 04 11:07:20 2019 UTC - Audio client started: 0x00E5FE28, 1
Fri Oct 04 11:07:21 2019 UTC - Game is using dxgi (dx10/dx11), preparing to hook.
Fri Oct 04 11:07:21 2019 UTC - hookCreateDXGIFactory called
Fri Oct 04 11:07:21 2019 UTC - Hooking vtable for factory
Fri Oct 04 11:07:21 2019 UTC - DXGIFactory2_CreateSwapChain already hooked via IDXGIFactory or IDXGIFactory1
Fri Oct 04 11:07:21 2019 UTC - hookCreateDXGIFactory1 called
Fri Oct 04 11:07:21 2019 UTC - Hooking vtable for factory
Fri Oct 04 11:07:21 2019 UTC - DXGIFactory1_CreateSwapChain already hooked via IDXGIFactory or IDXGIFactory2
Fri Oct 04 11:07:21 2019 UTC - DXGIFactory2_CreateSwapChain already hooked via IDXGIFactory or IDXGIFactory1
Fri Oct 04 11:07:21 2019 UTC - hookCreateDXGIFactory called
Fri Oct 04 11:07:21 2019 UTC - Hooking vtable for factory
Fri Oct 04 11:07:21 2019 UTC - DXGIFactory2_CreateSwapChain already hooked via IDXGIFactory or IDXGIFactory1
Fri Oct 04 11:07:24 2019 UTC - Hooking child launched from ShellExecuteExA: H:\Steam\steamapps\common\Close Combat - The Bloody First\CC_TBF_STEAM.exe
Fri Oct 04 11:07:25 2019 UTC - Not hooking ShellExecuteExA
Fri Oct 04 11:07:25 2019 UTC - Hooking child launched from ShellExecuteExW: H:\Steam\steamapps\common\Close Combat - The Bloody First\CC_TBF_STEAM.exe
Fri Oct 04 11:07:25 2019 UTC - Not hooking ShellExecuteExW
Fri Oct 04 11:08:38 2019 UTC - Hooking child launched from ShellExecuteExA: H:\Steam\steamapps\common\Close Combat - The Bloody First\CC_TBF_STEAM.exe
Fri Oct 04 11:08:38 2019 UTC - Not hooking ShellExecuteExA
Fri Oct 04 11:08:38 2019 UTC - Hooking child launched from ShellExecuteExW: H:\Steam\steamapps\common\Close Combat - The Bloody First\CC_TBF_STEAM.exe
Fri Oct 04 11:08:38 2019 UTC - Not hooking ShellExecuteExW
Fri Oct 04 11:08:57 2019 UTC - Hooking child launched from ShellExecuteExA: H:\Steam\steamapps\common\Close Combat - The Bloody First\CC_TBF_STEAM.exe
Fri Oct 04 11:08:57 2019 UTC - Not hooking ShellExecuteExA
Fri Oct 04 11:08:57 2019 UTC - Hooking child launched from ShellExecuteExW: H:\Steam\steamapps\common\Close Combat - The Bloody First\CC_TBF_STEAM.exe
Fri Oct 04 11:08:57 2019 UTC - Not hooking ShellExecuteExW
Fri Oct 04 11:09:26 2019 UTC - Hooking child launched from ShellExecuteExA: H:\Steam\steamapps\common\Close Combat - The Bloody First\CC_TBF_STEAM.exe
Fri Oct 04 11:09:26 2019 UTC - Not hooking ShellExecuteExA
Fri Oct 04 11:09:26 2019 UTC - Hooking child launched from ShellExecuteExW: H:\Steam\steamapps\common\Close Combat - The Bloody First\CC_TBF_STEAM.exe
Fri Oct 04 11:09:26 2019 UTC - Not hooking ShellExecuteExW
Fri Oct 04 11:09:46 2019 UTC - Hooking child launched from ShellExecuteExA: H:\Steam\steamapps\common\Close Combat - The Bloody First\CC_TBF_STEAM.exe
Fri Oct 04 11:09:46 2019 UTC - Not hooking ShellExecuteExA
Fri Oct 04 11:09:46 2019 UTC - Hooking child launched from ShellExecuteExW: H:\Steam\steamapps\common\Close Combat - The Bloody First\CC_TBF_STEAM.exe
Fri Oct 04 11:09:46 2019 UTC - Not hooking ShellExecuteExW
Fri Oct 04 11:10:45 2019 UTC - GameOverlayRenderer.dll detaching

[wodin]

Seems it can be an issue with Steam...

https://steamcommunity.com/app/386800/d ... 405/?ctp=2

#Seems like I'll never get CC to run unless and do a full reinstall of WIn10...

Going to run some scans and registry cleaner apps...see what happens.

[wodin]

Hmmm...running Roguekiller and strangely it's flagged the autorun.exe as VT.Unknown...wanted to know if it should upload to website as possible virus! Never had this happen with Roguekiller and a game before..

[wodin]

Found this error log and the trace error log in post below this one in actual CCTBF core folder. Not in Documents\Saved Games...


ERROR
Steam Startup Error
(0) : Failed
ERROR

######## EXCEPTION: 0x80000003 at address: 0x006172AD
Starting Debugger
SEARCHING: D:\Games\Perforce Workspace\CloseCombat\TBF;D:\Games\Perforce Workspace\CloseCombat\TBF;C:\WINDOWS
D:\Games\Perforce Workspace\CloseCombat\TBF;D:\Games\Perforce Workspace\CloseCombat\TBF;C:\WINDOWS
SGA: KernelErrorHandler
KernelErrorHandler
c:\dev\kernel\kernelerror.cpp(276) : +0 bytes (KernelErrorHandler) 0
SGA: Error
Error
c:\dev\kernel\kernelerror.cpp(136) : +17 bytes (Error) 0
SGA: EntryPoint
EntryPoint
c:\dev\closecombat\game\system.cpp(1136) : +10 bytes (EntryPoint) 0
SGA: WinMain
WinMain
c:\dev\archon\platform_windows.cpp(559) : +9 bytes (WinMain) 0
SGA: __tmainCRTStartup
__tmainCRTStartup
f:\dd\vctools\crt_bld\self_x86\crt\src\crtexe.c(578) : +29 bytes (__tmainCRTStartup) 0
SGA: BaseThreadInitThunk
BaseThreadInitThunk
SGA: RtlGetAppContainerNamedObjectPath
RtlGetAppContainerNamedObjectPath
SGA: RtlGetAppContainerNamedObjectPath
RtlGetAppContainerNamedObjectPath
Debugger Cleanup

[wodin]

######## EXCEPTION: 0x80000003 at address: 0x006172AD
Starting Debugger
SEARCHING: D:\Games\Perforce Workspace\CloseCombat\TBF;D:\Games\Perforce Workspace\CloseCombat\TBF;C:\WINDOWS
D:\Games\Perforce Workspace\CloseCombat\TBF;D:\Games\Perforce Workspace\CloseCombat\TBF;C:\WINDOWS
SGA: KernelErrorHandler
KernelErrorHandler
c:\dev\kernel\kernelerror.cpp(276) : +0 bytes (KernelErrorHandler) 0
SGA: Error
Error
c:\dev\kernel\kernelerror.cpp(136) : +17 bytes (Error) 0
SGA: EntryPoint
EntryPoint
c:\dev\closecombat\game\system.cpp(1136) : +10 bytes (EntryPoint) 0
SGA: WinMain
WinMain
c:\dev\archon\platform_windows.cpp(559) : +9 bytes (WinMain) 0
SGA: __tmainCRTStartup
__tmainCRTStartup
f:\dd\vctools\crt_bld\self_x86\crt\src\crtexe.c(578) : +29 bytes (__tmainCRTStartup) 0
SGA: BaseThreadInitThunk
BaseThreadInitThunk
SGA: RtlGetAppContainerNamedObjectPath
RtlGetAppContainerNamedObjectPath
SGA: RtlGetAppContainerNamedObjectPath
RtlGetAppContainerNamedObjectPath
Debugger Cleanup

[zakblood]

need pipfromslitherine etc or a developer for that as i don't know the code base

[PipFromSlitherine]

What happens if you try and run the EXE itself from the install folder? And is the timestamp on the error log appropriate for when you are trying to run the game?

Cheers

Pip