Game instantly closes.

[joelapeno]

Whenever I start my game, it instantly closes 2 seconds after opening, no update screen, no login screen nothing, just instantly closes. I've reinstalled, deleted all fantasy grounds files, I've updated all my drivers, nothing works.


__________________________________________Update.t xt file______________
https://pastebin.com/Yn7pNNDx


________________________________
Console.txt file
___________
[07.07.2019 20:00:09] Runtime Notice: Initializing DirectX
[07.07.2019 20:00:09] Runtime Notice: Initializing COM


________________________


If anything else is needed let me know.

[Zacchaeus]

What type of computer are you using (PC or mac). What operating system are you using? Do you have full read/write permission to the install directory? Are you installing in the default locations or elsewhere?

[joelapeno]

PC, w10 home 64-bit, full permissions, I've installed through steam and the website to my normal C Drive, I've tried installing to my other hard drives as well, nothing has worked.

[Zacchaeus]

Can you look in your FGData directory (default %Appdata%/Roaming/Fantasy Grounds) and see if the console.log file shows any error messages recorded there.

It is possible that it is a graphic driver issue if your graphics driver doesn't handled DX9 too well; but there should be some kind of error generated if that is the case.

[joelapeno]

I pasted it in the OP, it just says

Console.txt file
___________
[07.07.2019 20:00:09] Runtime Notice: Initializing DirectX
[07.07.2019 20:00:09] Runtime Notice: Initializing COM

and then nothing else

[Zacchaeus]

Looks like it is failing to initialise the COM libraries. I’m not at all sure what the fix for that is.

[Moon Wizard]

The message occurs prior to loading, but a separate error message is generated if COM initialization failed. COM is used to attempt automatic port forwarding configuration on the router via UPnP.

* Can you show a screenshot of your FG application directory and FG data directory?
The default locations for these on Windows are: "C:\Program Files (x86)\Fantasy Grounds\" and "C:\Users\<UserName>\AppData\Roaming\"

* We had another user with a similar issue that solved it by downloading the most up-to-date graphics drivers for their video card.

Regards,
JPG

[joelapeno]

Thanks for the reply, but I just updated, but I can try reinstalling and I'll let you know if that works.

[joelapeno]

27823 Program Files
27824 Roaming
both screenshots are here

[damned]

Can you please post your FG Settings from the Setup option too please?

[joelapeno]

I'm sorry, but where can I find that?
edit: I think this might be what you're talking about? 27825

[Moon Wizard]

Hmm, I'm at a bit of a loss as to why this would fail.

One thing I just noticed in the original log file is that your configuration is reporting that you are running on a version of Windows 8 that is not supported by Microsoft. Is there a reason why you haven't updated to Windows 8.1 which is in extended support from Microsoft and is still a free upgrade from what I've read?

Regards,
JPG

[joelapeno]

I'm not even on windows 8, I'm on windows 10 Home 64-bit

[Trenloe]

Have you tried running the installer from the main FG web page, here's the link: https://www.fantasygrounds.com/filelibrary/FGWebInstall.exe

I'd recommend uninstalling the Steam version first (it's just a stub to FG, but still worth uninstalling). In theory it should give the same app, but worth a try I think...

[joelapeno]

Yup, I've done that as well, same problem arises :(

[Trenloe]

What security and anti-virus applications do you have on your PC?

[Trenloe]

Also, does the Windows application event viewer show an entry when FG closes?

[joelapeno]

Just, windows security

[Moon Wizard]

Apologies for the red herring on the Windows version. I just did some research, and there is some esoteric reason why it returns an older OS version from the Microsoft API, even when running a newer version. Not relevant to your issue. I was just looking for any possibility why it wouldn't run.

We're trying to determine what is different on your system that might be causing issues. Can you bring up System Information app on Windows, and provide the following details? (screenshot or typing)

System Summary
OS Name
Version
System Type
Processor

Components/Display
Name
Adapter Type
Driver Version

Thanks,
JPG

[joelapeno]

Not a problem.

System Summary
OS Name: Microsoft Windows 10 Home
Version: 10.0.18362 Build 18362
System Type: x64-based PC
Processor: AMD Ryzen 7 2700x Eight-Core Processor...

Components/Display
Name: NVIDIA GeForce GTX 1060 6GB
Adapter Type: GeForce GTX 1060 6GB, NVIDIA compatible
Driver Version: 26.21.14.3086

[Moon Wizard]

Hmm, I also have NVidia (1080) and x64 with same Windows build. I just updated my graphics drivers to match your version, and I was able to run successfully. The only difference is that I have Intel CPU.

Can you try manually deleting the files (FantasyGrounds.exe, D3DX9_43.dll) from C:\Program Files (x86)\Fantasy Grounds\; and then running FGUpdaterEngine.exe to download a fresh version?
(I think you already mentioned doing a new install, but this ensures that the files are actually deleted (and not just attempted to be deleted).)

I'm sort of guessing at what might be causing the issue at this point. If this doesn't work, I might have to try making a custom build in the Dev channel for you to try with extra console output during initialization.

Regards,
JPG

[Trenloe]

Did you see if there was anything in the Windows Application Event Viewer (I mentioned in post #17 above)?

[joelapeno]

#21 Did not work and #22 there actually is an error
Faulting application name: FantasyGrounds.exe, version: 0.0.0.0, time stamp: 0x5c1cac26
Faulting module name: Wintab32.dll, version: 1.5.0.0, time stamp: 0x5c1738bf
Exception code: 0xc0000005
Fault offset: 0x00001548
Faulting process id: 0x2190
Faulting application start time: 0x01d535ff38e40f3b
Faulting application path: C:\Program Files (x86)\Steam\steamapps\common\Fantasy Grounds\FantasyGrounds.exe
Faulting module path: C:\Windows\SYSTEM32\Wintab32.dll
Report Id: d4ead1fe-3c97-4981-bead-bbe0b1b5ac99
Faulting package full name:
Faulting package-relative application ID:

[Trenloe]

Faulting module name: Wintab32.dll, version: 1.5.0.0...
Wintab32.dll is a file used by device drivers for Wacom products - things like tablet/pointer devices.

Do you have any such device from Wacom installed? Or, have at some point installed Wacom software?

[joelapeno]

that was actually it, I just uninstalled and it worked! awesome thanks so much, it was an xp pen tablet in case you need that for the future

[Moon Wizard]

FG will attempt to load wintab32.dll, if it exists. And that happens right after the COM initialization. This file doesn't even exist on my computer.

Perhaps the wintab32.dll file on your computer got corrupted; or the one installed uses a different tablet API than FG is expecting?

I'm wondering if it might be time to rip out the tablet interface code, since it was written 12 years ago; and probably doesn't even work anymore...

Regards,
JPG

[Moon Wizard]

I just pushed a beta build of v3.3.8 into our Test channel, which removes this very old code that caused this issue.

Thanks for your patience,
JPG

[joelapeno]

thank you for the help!