Progammable Shaders, essential?

[Serin]

the biggest thing i see is antialiasing its not a setting in the GPU so i know thats why the default crashes with that setting, is it possible that the custom clients have it on by default?

anyways luckily the default client works, and its resizable now!

[loftar]

the biggest thing i see is antialiasing its not a setting in the GPU so i know thats why the default crashes with that setting, is it possible that the custom clients have it on by default?

In that case, they should crash with the same error as the default client does when you turn antialiasing on, which is clearly not the case.

[romovs]

Probably Windows' supplied OpenGL driver is been loaded for some reason when using custom client while default one loads a proper driver. Maybe there is some difference between WebStarted apps vs javaw/java that affects this choice for Windows?
IIRC it helped someone having this exact issue just to install 64-bit Java and 64-bit Intel drivers from Intel website.

[APXEOLOG]

Probably Windows' supplied OpenGL driver is been loaded for some reason when using custom client while default one loads a proper driver. Maybe there is some difference between WebStarted apps vs javaw/java that affects this choice for Windows?
IIRC it helped someone having this exact issue just to install 64-bit Java and 64-bit Intel drivers from Intel website.

There was a bug in some versions on jre8 under Win10 (http://forum.jogamp.org/Bad-GL-RENDERER-detection-td4036346.html#a4036360)
I think i used java 8u25 release to launch the client th that case, the bug was not present here

[Serin]

well currently the run.bat is going to javaw; im about to try v8u25 and alter the path to see if that makes a difference or at least changes the error

Edit: Didn't even have to change the path the issue was indeed the java version

[loftar]

There was a bug in some versions on jre8 under Win10 (http://forum.jogamp.org/Bad-GL-RENDERER-detection-td4036346.html#a4036360)
I think i used java 8u25 release to launch the client th that case, the bug was not present here

Interesting; that seems to be the same bug I encountered in my last little experiment with Windows. At that time, I concluded that it was a bug in Intel's drivers for old enough GPUs, which only surfaced on Windows 10. Not sure if that conclusion is correct, of course, but if it is, then it could be that they no longer test those older GPUs on Windows 10.

[sMartins]

they no longer test those older GPUs on Windows 10.

Why should they do that? You have always to buy the new....keep the wheels of economy rolling (this is always Italian )