Issues with "Threading" on Windows (any flavor)? Please post here

Store Page

Tabletop Simulator

All Discussions Screenshots Artwork Broadcasts Videos Workshop News Guides Reviews

Tabletop Simulator > General Discussions > Topic Details

Dan

4 Jan, 2016 @ 12:09pm

Issues with "Threading" on Windows (any flavor)? Please post here

Happy New Year!

If you're having issues with threading on any flavor of Windows, please post here so I can contact you and try to resolve the issue.

Now that we're back in the office for 2016, we'd like to resolve the last few remaining issues that people are having with the multi-threaded mod loading. Turning threading off is not the permanent solution/work-around for us. So please post here if you have the issue and are able to donate some time to helping us figure out the last puzzle piece.

Thanks!

< >

Showing 1-6 of 6 comments

DrakeFox

4 Jan, 2016 @ 1:07pm

I had issues today when trying to load images from file:// URIs. Though considering my system is quite old, you might not care for my input. But if there's anything I can do to help, I will.

System:
Intel Q9300 @2.5ghz
6gb DDR3 ram
Zotac GeForce 465GTX
Windows Vista Home Premium x64

SecurityDog has Tabletop Simulator

4 Jan, 2016 @ 2:21pm

Having the same problem. I have win10, i7 2600, 8gb ram, geforce gtx 970.

SecurityDog has Tabletop Simulator

4 Jan, 2016 @ 3:39pm

It works now for me after uninstall the C++ Redistributable 2012 and install it again :)

Marquise*

4 Jan, 2016 @ 8:11pm

HAPPY NEW YEAR and thank-you

DrakeFox

4 Jan, 2016 @ 10:15pm

Just tested out this morning, uninstalled VS2012 x86 + x64. Reinstalled x86, x64, reboot. Still no luck with threading.
Though, if you disable threading, load a game it'll load up fine. Quit to main menu, enable threading, load same workshop mod and it'll seem to work, I'm guessing because of cache.

A quick peek with Process Monitor shows it trying to load the files.
Highlighted a specific file, it seems to start with an overflow on QueryInformationVolume and QueryAllInformationFile, then successful ReadFile in 16383 length chunks until a successful CloseFile. That should be how it should behave I'm sure.

If there's anything else I can do to assist, please let me know. For now, off to work.