I know it hasn't been much time, but any news on fixing the driver crashing on Intel Graphics 4000 HD Mobile?
Reference link: p/4178495
Reference link: p/4178495
directX overall lags way more than opengl, because of how much its depended on a single core performance, rendering 80-100% cpu1 load and framelaggingpeppy wrote:
same spikes are not present in direct x?_index wrote:
yes, on both
frame limiter doesnt help, however issue seems to be totally random, sometimes appearing for a few hours and sometimes not. cpu load is usually at 70% one core and 20-30% other cores, while gpu stays about 50-60%
Yes I did. I wish I could record it, but that won't show much as the recording cuts as soon as it crashes.peppy wrote:
abraker: Did you even test before posting? HD4000 has been reported fixed by other users.
Graphics: [Tom94] Improve behavior of resetting the screen resolution to desktop settings. (fixes /t/259747)Reference post: p/4158960
New update, still the same issue. Screenshot taken from the fresh install. Issue still happens too on my main directory.peppy wrote:
@fr33z3r: need an update on whether things are looking any better now.
Do you by any chance have GX mode enabled? Could you describe a bit more exactly what kind of popping you experience? I also have an STX and do not get any such things.Bmxant wrote:
I'm having issues with occasional sound popping. Issues only occurs in Osu!, no other game or sound file. It's random, but very noticeable and annoying.
Using a Xonar STX
Can reproduce the problem using both the Beta and Cutting-edge build
I don't seem to have the issue using the Stable client (so far)
Thanks for the reply, Tom94.Tom94 wrote:
Do you by any chance have GX mode enabled? Could you describe a bit more exactly what kind of popping you experience? I also have an STX and do not get any such things.Bmxant wrote:
I'm having issues with occasional sound popping. Issues only occurs in Osu!, no other game or sound file. It's random, but very noticeable and annoying.
Using a Xonar STX
Can reproduce the problem using both the Beta and Cutting-edge build
I don't seem to have the issue using the Stable client (so far)
Thanks a lot for the detailed information! I hear what you mean and will try to reproduce and look into it when it find the time.Bmxant wrote:
Pop/distort sound is at 0:31
https://www.youtube.com/watch?v=hCV06IM ... e=youtu.be
Application: osu!.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at OpenTK.Graphics.OpenGL.GL.GenBuffers(Int32, Int32 ByRef)
at #=qye0$5YzUohuFy0qK3Za7DiKyzeAlwodjqvDQZfm$HquzOWcW$YiBeK2gt5l4Cpgn.#=qj5RzzukSvCEAK8mrB4nHsw==()
at #=qYXxbL8qIL6wewuGnq7zT2g==.#=qj5RzzukSvCEAK8mrB4nHsw==()
at #=qGDXvskXP5HpR5NXG0JB9iQDg1aJEao7jWVFxAxjte40=.#=qeUlHWXdBKhAVDyWeU2F5Vg==()
at #=qnkb9whIkP9kmVLKYGzx3fA==.#=qKMe5x3OHNZe6N44TOzJJkw==(System.String, Boolean, Boolean, Boolean)
at #=qnkb9whIkP9kmVLKYGzx3fA==.#=qNv9AY$nrGIhAPK9YlteP4w==(System.String[])
at #=qnkb9whIkP9kmVLKYGzx3fA==.#=q0WrRcV01CL0r5Ftd$XtIEw==()
at #=qzuZqONQlNterlD6omxQ0Yf$k9FHWxTwA19sWgYs9vj4=.#=qYSqKQhx$diQxrdfMePEwAQ==()
I looked into this issue and the new VBO code requires a higher version of OpenGl to run. Your graphics card needs to support at least OpenGl 1.5 in order to run the current code implementation. We will need to think of an alternative for GMA / ATI cards if we want to keep support for those models. Here is a link describing the compatibility issue.Winshley wrote:
I posted this few days ago, telling me to post the issue here instead.
The game was running fine 3 weeks ago, but went on hiatus for a while before returning again. I went through all the updates, showing osu! splash screen, only to get itself exploded. Below is the error message I got from Event Viewer:Application: osu!.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at OpenTK.Graphics.OpenGL.GL.GenBuffers(Int32, Int32 ByRef)
at #=qye0$5YzUohuFy0qK3Za7DiKyzeAlwodjqvDQZfm$HquzOWcW$YiBeK2gt5l4Cpgn.#=qj5RzzukSvCEAK8mrB4nHsw==()
at #=qYXxbL8qIL6wewuGnq7zT2g==.#=qj5RzzukSvCEAK8mrB4nHsw==()
at #=qGDXvskXP5HpR5NXG0JB9iQDg1aJEao7jWVFxAxjte40=.#=qeUlHWXdBKhAVDyWeU2F5Vg==()
at #=qnkb9whIkP9kmVLKYGzx3fA==.#=qKMe5x3OHNZe6N44TOzJJkw==(System.String, Boolean, Boolean, Boolean)
at #=qnkb9whIkP9kmVLKYGzx3fA==.#=qNv9AY$nrGIhAPK9YlteP4w==(System.String[])
at #=qnkb9whIkP9kmVLKYGzx3fA==.#=q0WrRcV01CL0r5Ftd$XtIEw==()
at #=qzuZqONQlNterlD6omxQ0Yf$k9FHWxTwA19sWgYs9vj4=.#=qYSqKQhx$diQxrdfMePEwAQ==()
Makes sense.TheVileOne wrote:
I looked into this issue and the new VBO code requires a higher version of OpenGl to run. Your graphics card needs to support at least OpenGl 1.5 in order to run the current code implementation. We will need to think of an alternative for GMA / ATI cards if we want to keep support for those models. Here is a link describing the compatibility issue.
smoogipooo wrote:
@Winshley: Please test again
System.ArgumentException: Version string portion was too short or too long.
at System.Version.VersionResult.SetFailure(ParseFailureKind failure, String argument)
at System.Version.TryParseVersion(String version, VersionResult& result)
at System.Version.Parse(String input)
at System.Version..ctor(String version)
at #=q2RGho6OA$Q3AoWh_rJwdls32VE_DUTHpVM8biS5r4Po=.#=qHKbzGg9kaFcq$RuZ$p_8dQ==()
at #=qKj0H3V8xQ79JF8kPW$lQug==.#=qoP7fGILcSyqozyfclHWrIQ==()
at #=qKj0H3V8xQ79JF8kPW$lQug==.#=qnIX3ASoyevvlxD3AyiwggQ==()
at #=qPGkRY7FPh2MJQZJeBrF$erptF5ECo1MIGWucSoBgfUA=.#=q2duPe9AdIZmY9_cLc5rY2g==()
at #=qjU1NY2$E$b30iCIRJpxceA==.#=q4jFVuRSoX3GtOoihu0UHuw==(String #=q1zPTpHvpacVtwEgORwqMIw==, Boolean #=qpSA6cyZ7qdVcwC5yf4x88INfhNqLSul0BwL5gHAkXAc=, Boolean #=qay2a5Y_f6jY8_7K36ruRfUiyieYRHoScqyjtuUdP7FA=, Boolean #=qJmm0ixjT64t4slNnd2vSVg==)