Crispy

Resetting it to the original sony radeon driver and THEN uninstalling the whole radeon driver (o.O???) apparently fixed everything. It's starting now with the radeon gpu (at least as long as I keep bloom disabled). \o/

I'm currently installing the original sony radeon drivers again - let's see if I can change the gpu via hardware switch again after that. I'll definetly try to switch them in the bios, too, but probably not today. Thanks for helping, I'll keep you updated.

I didn't install any radeon driver, just intel. And the first two logs were when I tried another automatical driver update - which horribly broke, obviously. Edit: Radeon driver: date: 26.09.2011 version: 8.862.4.2000 (win tells me it's the latest version when I try to automatically update it) intel driver: date: 26.05.2015 version: 9.17.10.4229

Ok, seems like I fucked up big time. First of all: my hardware button for switching the gpus doesn't seem to work anymore, so you were right, of course with the radeon it's a different error message. Second: I tried to manually install the latest intel driver, after that (and while starting Avorion) my pc crashed with a bluescreen. So I reinstalled the driver I had, when I originally posted the question. Started Avorion. Bluescreen. But, the good news is: I have clientlogs of all these. :D Have fun with them, probably I'm just too silly to install a proper driver... Hm, seems like they just crashed together with my pc. They're mostly just this: Tue Oct 04 20:33:40 2016| Client started: "C:\Program Files (x86)\Steam\steamapps\common\Avorion\bin\Avorion.exe" "--serverpath=bin/AvorionServer.exe" Tue Oct 04 20:33:40 2016| Init Steamworks... ok Tue Oct 04 20:33:41 2016| Client Beta 0.9 r6050, running on Windows 7. Tue Oct 04 20:33:41 2016| CPU: GenuineIntel 4 Cores Tue Oct 04 20:33:41 2016| Getting display mode... ok Tue Oct 04 20:33:41 2016| Current display mode: 1920 x 1080 Tue Oct 04 20:33:41 2016| Creating settings... loading... ok Tue Oct 04 20:33:41 2016| Creating client window...Detected 2 displays Tue Oct 04 20:33:41 2016| Display 0: x: 0, y: 0, w: 1920, h: 1080 Tue Oct 04 20:33:41 2016| Display 1: x: 1920, y: 323, w: 1600, h: 900 Tue Oct 04 20:33:41 2016| Using display 0 Tue Oct 04 20:33:41 2016| Creating window, x: 0, y: 0, w: 1920, h: 1080... ok Tue Oct 04 20:33:42 2016| Creating GL context... ok Tue Oct 04 20:33:42 2016| Setting window mode WindowedSeamless... ok Tue Oct 04 20:33:42 2016| Creating client window ok Tue Oct 04 20:33:42 2016| Init shader level... ok Tue Oct 04 20:33:42 2016| Init rendering... starting rendering... initialize...OpenGL Context Information: Tue Oct 04 20:33:43 2016| Version: 3.1 Tue Oct 04 20:33:43 2016| VersionString: 3.1.0 - Build 9.17.10.4229 Tue Oct 04 20:33:43 2016| Vendor: Intel Tue Oct 04 20:33:43 2016| Renderer: Intel(R) HD Graphics 3000 Tue Oct 04 20:33:43 2016| GLSL Version: 1.40 - Intel Build 9.17.10.4229 Tue Oct 04 20:33:43 2016| Init GLEW... ok Tue Oct 04 20:33:43 2016| Init Debug Message Callback...No debug information callbacks available. Tue Oct 04 20:33:43 2016| ok Tue Oct 04 20:33:43 2016| Set VSync... ok Tue Oct 04 20:33:43 2016| Secure BackBuffer... ok Tue Oct 04 20:33:43 2016| Init Canvas...Create canvas of size 1920 x 1080... ok Tue Oct 04 20:33:43 2016| Init Canvas ok Tue Oct 04 20:33:43 2016| Init Refraction Texture... ok Tue Oct 04 20:33:43 2016| Init Post Processing... ok Tue Oct 04 20:33:43 2016| Init Debug Renderers... ok Tue Oct 04 20:33:43 2016| Rendering initialized Tue Oct 04 20:33:43 2016| Init rendering ok Tue Oct 04 20:33:43 2016| Check problematic drivers...Intel onboard graphics detected.These devices' OpenGL drivers can cause trouble with Avorion, since it's still in an early stage. Tue Oct 04 20:33:43 2016| If you run into graphics issues, please report them as a bug so we can fix them. Tue Oct 04 20:33:43 2016| EDIT: I just tried setting bloom back to true, now it's the same error message as in the first post. \o/ clientlog_Tue_Oct_04_20-33-40_2016.txt clientlog_Tue_Oct_04_20-07-57_2016.txt clientlog_Tue_Oct_04_20-06-23_2016.txt clientlog_Tue_Oct_04_20-05-31_2016.txt

Tried it, but then my intel-driver seems to crash. I just get a notification saying that my Intel driver is being restarted after crashing, even if I try the radeon gpu... :/

Hi everyone! I'm having trouble starting the beta version 0.9 on Win7. I have 2 GPUs, Intel HD 300 and Radeon HD 6630M and with both I'm getting the error message that my GPU doesn't support OpenGL 3.0. For Radeon, it looks like this: So I googled and found out that this GPU doesn't support OpenGL. Then I tried the onboard graphics: Then I googled again, after automatically updating my drivers, and installed the latest version of the intel driver for HD 3000 manually, which, as I read in another forum, should support OpenGL until 3.1. Still the same error message. The demo version from ~june worked just fine on my laptop, so I was wondering if you changed something major in the graphics. Clientlog is in the attachments (far too many characters :P) clientlog_Tue_Oct_04_17-59-34_2016.txt

Hello I am [insertNameHere] and I give good credit for buying cheap viagra for big spaceship! Msg me at certainly@notABot.to