And... I still can't update.
Screenshot:
Screenshot:
forum
[Archived] Issues with Latest Cutting-edge Build (Post Here)
posted
Total Posts
2,521
I felt small lags while playing, especially when I was looking at the approach circle.
This fix did not fix it for me. I switched back to cuttingedge build and onto the "Vsync" option, and now my frame rate is not limited properly. The FPS counter in the corner of the screen is displaying 100-150 fps (my monitor is 60Hz so it should be limiting at 60fps in vsync, which it still correctly does in stable build). It's acting the same way as "Unlimited".BanchoBot wrote:
Issue(s) in this thread have been addressed by the following changes:The changes will be applied to builds newer than b20150422.2cuttingedge.
- Fix VSync not working correctly and add support for non-60 fps monitors. (Tom94)
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
StockNine wrote:
And... I still can't update.
Screenshot:
I've been getting this thing where I will edit a map, but the second I open the Song Setup window, Osu! minimizes and proceeds to spawn infinate song setup windows in the upper left of my screen until it lags out and crashes my PC.
Hmm... Have you updated to the latest cutting edge build? I and others have experienced the same issue in the previous build (minus the PC crashing). However, since the last update, this issue has been resolved for me. I don't know, are others still experiencing this issue?PolkaMocha wrote:
I've been getting this thing where I will edit a map, but the second I open the Song Setup window, Osu! minimizes and proceeds to spawn infinate song setup windows in the upper left of my screen until it lags out and crashes my PC.
If it still continues, try windowed. That should help you at least for now.
It still happens; I've always used windowedburaimaster1234 wrote:
Hmm... Have you updated to the latest cutting edge build? I and others have experienced the same issue in the previous build (minus the PC crashing). However, since the last update, this issue has been resolved for me. I don't know, are others still experiencing this issue?PolkaMocha wrote:
I've been getting this thing where I will edit a map, but the second I open the Song Setup window, Osu! minimizes and proceeds to spawn infinate song setup windows in the upper left of my screen until it lags out and crashes my PC.
If it still continues, try windowed. That should help you at least for now.
Adding onto my last post (issue under WINE): It seems like it tries to swap the resolution of the two monitors. My large monitor gets set to 1024x768 and they both get put into panning mode with a virtual 1920x1080 resolution.That is, I have a 2048x768 visible area at all times spread across both my monitors, mapped to a virtual 2944x1024 area that can be scrolled with the cursor.Score_Under wrote:
- Osu! resizes the monitor it's run on to 1024x768
There doesn't seem to be a fullscreen/windowed toggle, which is unfortunate.
edit: switching to the beta channel gives me best of both worlds - working osu with no screen resolution changes, and borderless mode that supports losing focus under wine. I'll stay there for the time being.
Chat texture corruption bug still present:
https://img.cartooncraft.fr/3Xxh/70df60
EDIT: Here too https://img.cartooncraft.fr/N891/52a468
https://img.cartooncraft.fr/3Xxh/70df60
EDIT: Here too https://img.cartooncraft.fr/N891/52a468
ThePooN wrote:
Chat texture corruption bug still present:
https://img.cartooncraft.fr/3Xxh/70df60
EDIT: Here too https://img.cartooncraft.fr/N891/52a468
Same issue here as i said earlier.
- Had broken textures (white boxes on hitcircles/sliders, and main menu triangles didn't work (can't remember exactly what was wrong; i'll update later if I try it out again)
- No exclusive fullscreen mode (not sure if intentional or not; preferably I'd like to have exclusive fullscreen over borderless though)
- As a result of no fullscreen mode; AMD VSR resolutions aren't usable (which isn't a huge concern at all for a majority of people/cases; pretty sure nobody cares about downsampling osu! :p)
- osu! started on the non-primary screen (I use 3 monitors; center is primary, but osu! started on the left monitor; haven't tried using the cfg to change this, but Stable and Beta builds automatically choose center)
- No exclusive fullscreen mode (not sure if intentional or not; preferably I'd like to have exclusive fullscreen over borderless though)
- As a result of no fullscreen mode; AMD VSR resolutions aren't usable (which isn't a huge concern at all for a majority of people/cases; pretty sure nobody cares about downsampling osu! :p)
- osu! started on the non-primary screen (I use 3 monitors; center is primary, but osu! started on the left monitor; haven't tried using the cfg to change this, but Stable and Beta builds automatically choose center)
Issue(s) in this thread have been addressed by the following changes:
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
- Fix various exclusive fullscreen issues. (Tom94)
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
Hello again. So I don't know if this is already a known issue or not, but in spectator mode, the skip button remains during game play. I remember this occurring in previous builds. Unfortunately, I do not know how to replicate, except that it appears to be random.
This was just after updating to the latest cutting edge build.
Screenshot:
This was just after updating to the latest cutting edge build.
Screenshot:
While it's not quite clear what "Various exclusive fullscreen issues" means exactly, it didn't seem to do anything for me at least. It still looks and stutters the same as before.
Can confirm this happening randomly on IRC, PMs and channels.Kogarou- wrote:
I didnt even play, just opened osu! and said hello to tom
release b20150423cuttingedge
ce.b20150423
Also, game minimizes upon losing focus on native screen resolution (borderless windowed mode) only and it's getting extremely annoying
@edit
seriously why would you even go the oGL way if you already had DX figured out
I see some serious tearing post-switch
@edit 2.0
@moar edit
Can confirm not happening only with nicknames
Topic Starter
My problem just happened again and I'm not sure why. Each time I let cutting edge receive an update not of the beatmaps load when I try to play. The beatmap count not be loaded successfully notification displays. It fixes itself when I go back to a different build and update to cutting edge. It doesn't affect my debug build, possibly because it doesn't receive files in this way.
so this is the go to for posting CE build issues eh?
well, i would like to report a still on-going issue with the triangles. after a while of running, FPS drops down from greater then 130 to around 30-40 fps. on top of that, my computer gets hot. all this happens after a couple minutes of runtime. it isnt thermal throttling becuase whenever that happens, my fps drops down to about 3-5fps at couple-second intervals.
usually thermal throttling or overheating doesn't happen unless i play demanding games like crysis, battlefield, mirrors edge, ETC.; and even then, i have my laptop sitting on a cooling pad
i remember thevileone mentioned that the performance issue was fixed. but i wonder if certain GPU's still have a compatability issue.
-----
i run unlimited FPS with directx render. i dont run opengl
all the eye candy is disabled (shaders, lighting effects, you name it) so i can run osu with no FPS drops.
i use Veilstars skin on his user page.
i run a DELL INSPIRON N7110 16:9 widescreen laptop
with the stable and beta build, i can get up to 150-200fps easy while capping at a cool and stable temperature, but still; cutting edge is cutting edge =S
well, i would like to report a still on-going issue with the triangles. after a while of running, FPS drops down from greater then 130 to around 30-40 fps. on top of that, my computer gets hot. all this happens after a couple minutes of runtime. it isnt thermal throttling becuase whenever that happens, my fps drops down to about 3-5fps at couple-second intervals.
usually thermal throttling or overheating doesn't happen unless i play demanding games like crysis, battlefield, mirrors edge, ETC.; and even then, i have my laptop sitting on a cooling pad
i remember thevileone mentioned that the performance issue was fixed. but i wonder if certain GPU's still have a compatability issue.
-----
i run unlimited FPS with directx render. i dont run opengl
all the eye candy is disabled (shaders, lighting effects, you name it) so i can run osu with no FPS drops.
i use Veilstars skin on his user page.
i run a DELL INSPIRON N7110 16:9 widescreen laptop
System Specifications
- operating system
- [list:1337]Windows 7 Home Premium 64-bit SP1
- CPU
- [list:1337]Intel Core i5 2430M @ 2.40GHz
Sandy Bridge
- RAM (if its necessary)
- [list:1337]8.00GB Dual-Channel DDR3 @ 664MHz
- GPU
- [list:1337]Intel HD Graphics 3000
with the stable and beta build, i can get up to 150-200fps easy while capping at a cool and stable temperature, but still; cutting edge is cutting edge =S
Foolish me. Why don't I use the search function on the website? ...VeilStar wrote:
A known issue. Not cuttingedge specific though. See t/215455buraimaster1234 wrote:
<spectator skip button stuff>
Anyway, I thought this was an isolated incident restricted to a certain beatmap of mine, but popup windows in the editor (both borderless and bordered) remain inactive. I guess this is a rehash of what PolkaMocha already reported.
Strangely, this was fixed for me (see my response to PolkaMocha), but then suddenly began to reoccur. I don't remember if this was just after I updated to a newer build or what.
Also, this has happened across beatmaps and computers, just something to note.
Those "various exclusive fullscreen issues" seem to make osu! minimize when alt tabbed or "loses focus" as said earlier. Which is rather inconvenient and annoying now.
I also have the screen tearing issue in the latest cutting edge build. VSync, however, works fine for me but since I can't really play with that delay I will probably just go back to the stable build until the issue is fixed.
OS: Windows 7 SP1 x64
CPU: AMD FX-8320 (8 cores @3.50 GHz)
GPU: Nvidia GTX-660
Screen: Acer S242HL 60Hz (Playing fullscreen, 1920x1080)
OS: Windows 7 SP1 x64
CPU: AMD FX-8320 (8 cores @3.50 GHz)
GPU: Nvidia GTX-660
Screen: Acer S242HL 60Hz (Playing fullscreen, 1920x1080)
I don't know what happened to cutting edge build, but now, I can't put it anymore into fullscreen mode, and that makes it not very smooth, and add a very noticeable input lag making cutting edge build not enjoyable. I'll switch to beta as it still can be put to fullscreen, but if someday this comes to stable it'll meens I'll have to stop playing because of this input lag. My FPS are not realy low, they are like 250ish (They were 300ish with DirectX fullscreen before and still are on Beta or Stable) but my cursor act strangely, like it's delayed and that makes the game almost unplayable. Also, when looking auto playing, I had the feeling that framerate was not stable and had some very short lag spikes.
If you have some idea why I'll put my system specs here :
Windows 8.1
16GB of RAM
Intel Core i7 4702MQ
Nvidia GT-750M with optimus
If you have some idea why I'll put my system specs here :
Windows 8.1
16GB of RAM
Intel Core i7 4702MQ
Nvidia GT-750M with optimus
You should be getting above 300fps with those specs, using only the integrated graphics. Try using only the integrated graphics of the CPU instead of the Nvidia GPU (GPU's that use optimus seem to have memory bandwidths much lower than their specifications).Arnold0 wrote:
I don't know what happened to cutting edge build, but now, I can't put it anymore into fullscreen mode, and that makes it not very smooth, and add a very noticeable input lag making cutting edge build not enjoyable. I'll switch to beta as it still can be put to fullscreen, but if someday this comes to stable it'll meens I'll have to stop playing because of this input lag. My FPS are not realy low, they are like 250ish (They were 300ish with DirectX fullscreen before and still are on Beta or Stable) but my cursor act strangely, like it's delayed and that makes the game almost unplayable. Also, when looking auto playing, I had the feeling that framerate was not stable and had some very short lag spikes.
If you have some idea why I'll put my system specs here :
Windows 8.1
16GB of RAM
Intel Core i7 4702MQ
Nvidia GT-750M with optimus
I have some REALLY bad tearing while playing. especially while spinnin my whole screen looks liek its cut into 3 differnet parts and glued again together... xD
V Sync is no option due to the input lag.. It WASNT like this before!
V Sync is no option due to the input lag.. It WASNT like this before!
wingman626 wrote:
well, i would like to report a still on-going issue with the triangles. after a while of running, FPS drops down from greater then 130 to around 30-40 fps.
This issue should be fixed. If it still happens to you it must be a different issue.wingman626 wrote:
i remember thevileone mentioned that the performance issue was fixed. but i wonder if certain GPU's still have a compatability issue.
There is no DirectX in the cuttingedge build. ???wingman626 wrote:
i run unlimited FPS with directx render. i dont run opengl
This is intended, for now at least, as OpenGL doesn't properly suport fulscreen. The current borderless should act as 'real' fullscreen though. Though if you have input lag while playing it doesn't. Is it like this on both your dedicated and integrated GPU? (Just wondering.)Arnold0 wrote:
I don't know what happened to cutting edge build, but now, I can't put it anymore into fullscreen mode
----
Not fixed on b20150423cuttingedge???BanchoBot wrote:
Issue(s) in this thread have been addressed by the following changes:The changes will be applied to builds newer than b20150421.7cuttingedge.
- Fix configuration/recovery dialog not working correctly. (peppy)
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
Serious question to devs (in general, especially whoever came up with this idea): why ditch DX in favor of oGL? Literally the only advantage is (better?) Linux support, but as a dev, I simply do not and more importantly cannot care about LinuxVeilStar wrote:
This is intended, for now at least, as OpenGL doesn't properly suport fulscreen. The current borderless should act as 'real' fullscreen though. Though if you have input lag while playing it doesn't. Is it like this on both your dedicated and integrated GPU? (Just wondering.)Arnold0 wrote:
I don't know what happened to cutting edge build, but now, I can't put it anymore into fullscreen mode
(also maybe macs but I'm not too sure on this one. Didn't peppy halt the development on the mac version?)
Will attempt to reproduce and edit post with resultsVeilStar wrote:
Not fixed on b20150423cuttingedge???BanchoBot wrote:
Issue(s) in this thread have been addressed by the following changes:The changes will be applied to builds newer than b20150421.7cuttingedge.
- Fix configuration/recovery dialog not working correctly. (peppy)
Please follow up in this thread if you believe more work needs to be done to fix the mentioned issues. If they have not yet been resolved, please provide any new details that may have arisen after this build.
you're not a very good dev then, lol.bigfeh wrote:
but as a dev, I simply do not and more importantly cannot care about Linux
Offering support for Linux isn't worth it if the other platforms suffer from it in any way - be it an API you can no longer use or a dependence you used to have that you had to get rid of because Linux.Microsoft Vista wrote:
you're not a very good dev then, lol.bigfeh wrote:
but as a dev, I simply do not and more importantly cannot care about Linux
Let me put it this way: All linux distros, combined, somehow manage to peek a bit over 1.5% global market share. Last I checked, Windows 7 alone had over half
There's really no problem in trying to support all platforms, but I don't see why OpenGL has to be forced just because of Linux if that's really the case. Can't it just be optional to choose between them? It was never really an issue to have it optional before. Granted that the old oGL wasn't that great afaik. But that shouldn't be an issue anymore.
peppy already answered why wants to use OpenGL:
The performance increase apparently needs some more testing, which is why there'll be DirectX on stable/beta until OpenGL is at least as good as DirectX, I think.peppy wrote:
cross platform support, better performance on all PCs (eventually), future proofing.
Thing is, it's really not that DX > oGL or anything, it's all down to the implementationSlasherZX wrote:
There's really no problem in trying to support all platforms, but I don't see why OpenGL has to be forced just because of Linux if that's really the case. Can't it just be optional to choose between them? It was never really an issue to have it optional before. Granted that the old oGL wasn't that great afaik. But that shouldn't be an issue anymore.
and the other thing is, osu!'s oGL implementation looks really, really bad.
As for choosing between them, there are quite a few gaping problems that arise with having different implementations for the same thing in different versions of the game. You could end up with two completely distinct games, code-wise
request to post this from my friend (because he can't lol), so:
"my osu! crashed while I pressed ctrl+z in the editor when I accidently placed a circle and inherited timing section. http://puu.sh/hqdbf/e8109c32f5.png and http://puu.sh/hqdgf/154fcccd22.png"
"my osu! crashed while I pressed ctrl+z in the editor when I accidently placed a circle and inherited timing section. http://puu.sh/hqdbf/e8109c32f5.png and http://puu.sh/hqdgf/154fcccd22.png"
Crash occurs everytime after Fraps is closed. Main cause is OpenTK.
Running Windows 8 Pro/Fraps 3.5.99 (latest)
Running Windows 8 Pro/Fraps 3.5.99 (latest)
Windows crash information
Problem signature:
Problem Event Name: BEX
Application Name: osu!.exe
Application Version: 1.3.3.7
Application Timestamp: 553b0e9f
Fault Module Name: FRAPS32.DLL_unloaded
Fault Module Version: 0.0.0.0
Fault Module Timestamp: 512c56b4
Exception Offset: 6ebf1ea0
Exception Code: c0000005
Exception Data: 00000008
OS Version: 6.2.9200.2.0.0.256.48
Locale ID: 1026
Additional Information 1: 5861
Additional Information 2: 5861822e1919d7c014bbb064c64908b2
Additional Information 3: 1a2a
Additional Information 4: 1a2aa8e38ac8adbb6fe1e594fa623c2e
Debug information pulled
AccessViolationException was unhandled
Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at OpenTK.Platform.Windows.Functions.SwapBuffers(IntPtr dc)
at OpenTK.Platform.Windows.WinGLContext.SwapBuffers()
at OpenTK.Graphics.GraphicsContext.SwapBuffers()
at #=qbB7axmsGD7MH$aJBFS3n8JG4D9DlyIG06gwgJKwyDD4=.#=qkXqXhXENNvvfPd1T9tLrag==()
at #=qffGv4fU91cYDyp9U3snhScIUOLqwqQZGKTdNsBBicq8=.#=q5v9K6Le1msGN66yEkFXlMQ==()
at #=qRio7xz2EyaOv$tv8xycHRQ==.#=qYeAGnBBoR4SbQiVMVswTbQ==()
at #=q9i439BqLzLKVKnJWszjqCpVeIqTEJERKE_D6RYM88W0=.#=q2J2aLctHuwy1K$L4fyhtUw==()
at #=q9i439BqLzLKVKnJWszjqCpVeIqTEJERKE_D6RYM88W0=.#=qHLWmOlq7xOMcGLlqNlwBew==(Object #=qiyZmoRVGhKzgH0TBgkDXZw==, EventArgs #=qezg1IIKwEwhQ4Kd$2$r_HQ==)
at #=qmK9RxUim$sdP_RZw1Um7ruiyzn6RJ1Cywz1Rv49hM9rZAaF8PNIWT_sG59$RXrxX.#=q28sc8wtGs7pTNVIkw_r3YQ==()
at #=q4lPYQR1rNVcvus2Dx1J7n25iMeU8CIEVC45pbj8UkQ6yA6bij2BSg34cbnz3VWt4.#=qoN1A0JrL_vdQxOlp02VvZnJc8q0BSSca8tVw5jJGiF4=(Object #=qwRcPw184ZDZcffZDfa4Uzg==, EventArgs #=qVPH1f6gYyiqJYIBFqHqLXA==)
at System.Windows.Forms.Application.ThreadContext.System.Windows.Forms.UnsafeNativeMethods.IMsoComponent.FDoIdle(Int32 grfidlef)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at #=q4lPYQR1rNVcvus2Dx1J7n25iMeU8CIEVC45pbj8UkQ6yA6bij2BSg34cbnz3VWt4.#=quzhJfQ7kbuHKezO_p3t0Vw==()
at #=q9i439BqLzLKVKnJWszjqCpVeIqTEJERKE_D6RYM88W0=.#=qUFoJaFQjr_S_3$QnVdeElQ==()
at #=q0p0_Jg37EJkfrlCoaRR_Ag==.#=qK3Bh1CcHdQphYICgJ2_g5g==(String #=qdQ6HUQQyDQ4pjmuURU_NvQ==, Boolean #=qjNcbvVFUbtv76ujk8LKN61LUpu_6hEjF5XKAm$TwEHM=, Boolean #=q9bhcfmjGZX$q3gQSVv1thTXz$zGLM_yS004gQq_HiPQ=)
at #=q0p0_Jg37EJkfrlCoaRR_Ag==.#=qS4rjc92thvVPIfv0b5hXxA==(String[] #=qH2WHpn$pHPGXCG$kCSUJLA==)
at #=q0p0_Jg37EJkfrlCoaRR_Ag==.#=qIB5g5Rvia_ifvdZwsYhtgQ==()
at #=q0CJ2dn4ZxmI7z4X4R$mBgRAsjUWN7CodF1H3wg7KwJQ=.#=qNSiWRbt1hQ9OyomqCG2ujw==()
cannot load the skin 