Algodoo Crashes on maiden launch every time windows 8.1

[Gearhead29]

Hello there I am a retuning user to the program,
I have had it previously on this laptop running on windows 7. The install runs fine but then crashes with the algodoo logo saying something like algodoo is starting for the first time this may take a couple of minutes please be patient.
I have tried a variety of different compatibility modes and running as admin and as regular, but nothing works any help would be appreciated.

[electronicboy]

Hello, chances are you've failed to upgrade the GPU drivers properly;

viewtopic.php?f=11&t=10150

If that doesn't work, please upload the log file stored in Documents/Algodoo.

[Gearhead29]

---------------------------------------
Algodoo v2.1.0, Win32
September 17 2014, 23:55:26
---------------------------------------
346 ms: Timer type: rdtsc
347 ms: Timer overhead: 10.25 ns
347 ms: Process attached to CPU 7
347 ms: CalcWorkDir
347 ms: GetExecutablePath
347 ms: Looking for DCS API...
347 ms: Failed to find DcsSdkDll.dll
347 ms: FileSystem::RenameFile: "Algodoo/Logfile_previous.txt" already existed.
347 ms: Permanently erasing file "Algodoo/Logfile_previous.txt"...
347 ms: Found 1 joystick
347 ms: ---
347 ms: Opened joystick 0
347 ms: Name: Unified Virtual HID
347 ms: Number of axes: 5
348 ms: Number of buttons: 16
348 ms: Number of balls: 0
348 ms: Number of hats: 1
348 ms: --
348 ms: Subsystem initialized
352 ms: ------------------------------------------------------
352 ms: CPU: Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz
352 ms: 8 cores at 2201 MHz
352 ms: CPU features:
352 ms: MMX - yes
352 ms: SSE - yes
352 ms: SSE2 - yes
352 ms: SSE3 - yes
352 ms:
352 ms: Windows 6.0
352 ms: ------------------------------------------------------
352 ms: argv[0] == "C:\Program Files (x86)\Algodoo\Algodoo.exe"
352 ms: Failed to open registry key: The system cannot find the file specified. (error code 00000002)
352 ms: Threadpool...
352 ms: Resources...
358 ms: Initializing Pango...
386 ms: Pango initialized
386 ms: Skin::OnSkinChange...
386 ms: Borders::Reload...
454 ms: Skin::RemakeTextDrawers...
454 ms: Looking for usable font...
530 ms: Simulation...
531 ms: SPH...
531 ms: Scene...
531 ms: Input...
531 ms: Classmate...
531 ms: GUI...
531 ms: Adding console...
531 ms: Adding Reflection...
531 ms: Adding Language...
531 ms: Adding Tools...
531 ms: Adding EntityModifier...
531 ms: Starting application...
531 ms: Loading chains...
544 ms: Loading Algodoo/chains/chain.phn...
544 ms: Deserializing code...
568 ms: Code deserialized
568 ms: Imported phunlet Algodoo/chains/chain.phn
573 ms: Loading Algodoo/chains/rope.phn...
573 ms: Deserializing code...
580 ms: Code deserialized
580 ms: Imported phunlet Algodoo/chains/rope.phn
585 ms: Initializing thread-pool...
586 ms: Application created
586 ms: Parsing Algodoo/thyme.cfg...
591 ms: Done parsing Algodoo/thyme.cfg.
591 ms: Parsing Algodoo/autoexec.cfg...
728 ms: Done parsing Algodoo/autoexec.cfg.
729 ms: First time running or new config - setting default window size
729 ms: Subsystem::CreateTheWindow
729 ms: Creating window...
1162 ms: * SCOPE BEGIN: QResizeEvent
1163 ms: QEvent::Resize from [-1, -1] to [1600, 900]
1163 ms: * SCOPE END: QResizeEvent
1163 ms: * SCOPE BEGIN: QTWindow::resizeEvent
1163 ms: * SCOPE END: QTWindow::resizeEvent
1163 ms: GLWidget::showEvent
1163 ms: Failed to connect to the SBSDK
1170 ms: Init GLEW...
1178 ms: Unloading GL resources...
1178 ms: Done Unloading GL resources
1178 ms: OSImpl::OnWindowCreated, hwnd = 000704F8
1178 ms: LoadTouchAPI
1178 ms: Touch API loaded.
1178 ms: Orientation locked to landscape
1179 ms: Looking for accelerometer...
1191 ms: Unable to find any sensors on the computer.
1191 ms: Window created.
1194 ms: Setting root container size to [1598, 898] (scale = 1)
1194 ms: Looking for tablet...
1194 ms: Wintab32.dll loaded
1194 ms: Tablet pen has normal pressure sensitivity
1194 ms: Tablet pen has orientation
1210 ms: Pen tablet acquired successfully

[Gearhead29]

I have updated drivers in the last 24 hours and all seemed to work fine except of course algodoo

[electronicboy]

Okay, I think algodoo doesn't even manage to find your GPU!

How are you updating your drivers, Just have to check...

And, what GPU are you using? Chances are you need to install the intel graphics accelerator if you don't have a dedicated GPU.

[Gearhead29]

Hey

I have a dedicated and integrated card in my machine, the dedicated card (the one that is currently active) is the AMD Raedon 6700M Series. I have tried updating through the windows service when that had no effect i went onto AMD and downloaded the newest catalyst suite for the card. Sorry for the delay I was away for the weekend

[electronicboy]

Windows update will only ever pull Microsofts junky drivers, not worth the space they take on the HDD.

I'd suggest uninstalling the official drivers and re-installing them, ensuring that your GPU is switched onto the dedicated and can't switch back, and seeing how that goes. For some reason, according to those logs, Algodoo isn't even finding a GPU, which would be the issue as there is no surface for it to render. My only guess would be that something, such as the GPU switch over program is causing issues with GPU detection, you might have to consider trying to disable one of the gpus fully in order to use Algodoo, openGL in these scenarios are never pretty, especially as they work so close to the hardware.