Restart osu! to force an update and post if it still happens (I think this is/was a problem with shaders because the resources didn't get updated correctly).
I get this when turning on shader effects in the cuttingedge build. (Though for rakosi2 it turns black.) Anyhow, turn that setting off untill it's fixed.cheeseandcereal wrote:
<stuff>
Still getting the issue here (after updating).smoogipooo wrote:
Restart osu! to force an update and post if it still happens (I think this is/was a problem with shaders because the resources didn't get updated correctly).
It seems to render shader effects to the wrong render target, an uninitialized one instead of the backbuffer.smoogipooo wrote:
Restart osu! to force an update and post if it still happens (I think this is/was a problem with shaders because the resources didn't get updated correctly).
serious question, how do you even output from an unitialized "buffer" without something noticing the fuckupNabile wrote:
It seems to render shader effects to the wrong render target, an uninitialized one instead of the backbuffer.smoogipooo wrote:
Restart osu! to force an update and post if it still happens (I think this is/was a problem with shaders because the resources didn't get updated correctly).
See:
Actually it's probably copying from the wrong render target instead of the backbuffer, instead of rendering to the wrong RT. Sorry about that.bigfeh wrote:
serious question, how do you even output from an unitialized "buffer" without something noticing the fuckup
smoogipooo wrote:
Restart osu! to force an update and post if it still happens (I think this is/was a problem with shaders because the resources didn't get updated correctly).
Oh, okay. I guess this makes more sense, though I'm really sleepy right nowNabile wrote:
Actually it's probably copying from the wrong render target instead of the backbuffer, instead of rendering to the wrong RT. Sorry about that.bigfeh wrote:
serious question, how do you even output from an unitialized "buffer" without something noticing the fuckup
Yup, the issue is fixed, thanks!smoogipooo wrote:
Update and let me know if the issue is still occurring, I've fixed up some things that could've caused this issue.
Are you using integrated graphics?Shizuyi wrote:
Now there is again the option to activate the fullscreen mode but if i activate it it seems to take no effect. Additional to that after every restart of osu the option is disabled again even if i enabled it before.
Could not reproduce. Fullscreen, however, did crash Windows Explorer, incorrectly detect my native screen resolution as 3840x2160 and most importantly break my multi-monitor setup. Twice.Shizuyi wrote:
Now there is again the option to activate the fullscreen mode but if i activate it it seems to take no effect. Additional to that after every restart of osu the option is disabled again even if i enabled it before.
No im using a GTX 780Ti.Tom94 wrote:
Are you using integrated graphics?Shizuyi wrote:
Now there is again the option to activate the fullscreen mode but if i activate it it seems to take no effect. Additional to that after every restart of osu the option is disabled again even if i enabled it before.
I switched back to CU just to see and yes the option does nothing and is untickied after a restart. However, it dosn't crash explorer and detected native resolution is good.Shizuyi wrote:
Now there is again the option to activate the fullscreen mode but if i activate it it seems to take no effect. Additional to that after every restart of osu the option is disabled again even if i enabled it before.
are you able to provide a copy of the skin folder which was triggering this issue?Mofo wrote:
Issues with Skin loading or such thing.
Error log: http://pastebin.com/EBCQZVyJ
Removing the entire skin folder does not work, shift back to stable mode works
While starting up stable mode i do get the message: Error loading skin configuration and if i look into skins list theres a blank file instead of default (Removed skin folder and automaticly remade a new one)
do you have vsync on? This happened to me with vsync on.Seri wrote:
Since the 27.04.2015 builds i experience many many microstutters, like one every few seconds. Didn't change anything in my setup.
EDIT: Didn't have any broken sliders since then though C:
Yep, also getting this when Evolve's overlay is enabled in-gameEspionage724 wrote:
Was wondering why my textures were broken, but it seems to be because of another program hooking it's overlay into osu! (Evolve). Upon closing Evolve, textures are fine.
Not sure if it's something osu! devs can fix or Evolve's devs (overlay worked fine on Stable and pre-OGL cutting-edge builds).
I'm using a Radeon HD 7850 on Windows 8.1 with Catalyst 15.4 if it matters.
on another note, playing like this is interesting :p
What gives yout that idea? This thread is for any issues with cutting-edge.baraatje123 wrote:
Note
This thread is ONLY for confirmable bugs; others also need to have it
I've been having this issue as well. The game stops and "osu! has stopped working" window pops up.award0707 wrote:
Since one of the latest cutting edge builds (from a few days ago?), the game sometimes crashes (i.e. the "error, click here to close program" dialog) when I press Ctrl-R to restart a map. I can't reproduce this bug at will though.
Same problem here.Dereku wrote:
Misc:
Triangles disappear before they come off the screen.
Mania:
Texture of long notes (sliders) disappears before the end of the note. http://youtu.be/hakzDXXg6s0
VC: ATI Radeon HD 4850
OS: Windows 8.1
Mania .ini are merged into skin.iniCheesecake_Hero wrote:
There is only one file in my osu folder with the .ini extension and that is the Skin.ini and there is not Mania keys Settings there.
Then i dont know what nK.ini Files are. There are no Mania File settings in my Skin,ini so i dont really know how to play CE with my Skins ;(marcostudios wrote:
Mania .ini are merged into skin.iniCheesecake_Hero wrote:
There is only one file in my osu folder with the .ini extension and that is the Skin.ini and there is not Mania keys Settings there.
ConfirmedVeilStar wrote:
On the results screen you can interact with the back button even if there are other clickable objects drawn in front/on top of it (such as usernames in chat). This doesn't happen with any other buttons, strangely. Cutting-edge specific, as I tried it in Stable but couldn't replicate it there.
https://www.youtube.com/watch?v=9yq_bRUUCPg
[General]
Name: Eye Friendly
Author: vahn10
Version: 2.2
SliderStyle: 2
CursorRotate: 1
CursorExpand: 0
CursorCentre: 1
AllowSliderBallTint: 1
[Colours]
Combo1: 255,152,65
Combo2: 166,197,73
Combo3: 134,224,187
Combo4: 175,205,250
Combo5: 246,175,250
Combo6: 175,205,250
Combo7: 134,224,187
Combo8: 166,197,73
SliderBorder: 0,170,128
//SongSelectActiveText: 255,255,0
SliderTrackOverride: 0,0,0
MenuGlow: 255,255,0
[Fonts]
HitCirclePrefix: Alternate Elements/Japanese Numbers (Heavenly Style)/default
HitCircleOverlap: 7
[General]
Name: 1
Author: various artists
SliderStyle: 2
SliderBallFlip: 1
CursorRotate: 1
CursorExpand: 1
CursorCentre: 1
SliderBallFrames: 1
HitCircleOverlayAboveNumer: 0
[Colours]
Combo1: 255,0,0
Combo2: 0,200,0
Combo3: 200,0,200
Combo4: 255,255,0
SliderBorder: 255, 255, 255
SliderTrackOverride: 0,0,0
SpinnerApproachCircle: 255,255,255
[Fonts]
HitCirclePrefix: default
HitCircleOverlap: 3
ScorePrefix: score
ScoreOverlap: -3
please update to the latest build and check for an error.txt in your skin folder after attempting to load it.Shizuku- wrote:
skins dont work
it appears fine here, albeit after the update process.VeilStar wrote:
Not sure if this is considered an issue or not, but the 'Recovery Dialog' (which is opened by holding SHIFT and opening osu!.exe) does not appear when on the cuttingedge release stream. Just thought i'd drop this in here as it's quite a handy thing to have in case something goes wrong.
Here goes:peppy wrote:
please update to the latest build and check for an error.txt in your skin folder after attempting to load it.
System.MissingMethodException: Method not found: 'Int32 System.Environment.get_CurrentManagedThreadId()'.
at #=qSE2myK38WFeUnS$I_ErmW1GSvY6S5dPQazK9A6jnVmkdpDZv2ypDuz_x7l2gXupT.#=qFgRk_vYkSlqfuPwFbLyO8SJY1BwKpOi7h_vFN9A2ers=..ctor(Int32 #=qNHTfHZo$Nmx$TazbGr9M9g==)
at #=qoVb1NirFIJvP_q0SCJvDHZxdthrNzpPG58EUSvq$HfI=.#=qZEfZFV69xxUVDwJk9q6NkQ==[T]()
at #=qS6_4R5k6pyioZEIEUBCrLeRk9NEQmt9cyj8Bh4V9qw8=.#=qunxcNqQq4qw01cZ0WKXWDA==()
at #=qoVb1NirFIJvP_q0SCJvDHZxdthrNzpPG58EUSvq$HfI=.#=q0AJdn6R1euYTDTUw3Ck98w==(String #=qszTF18FWf8i6AOUSHeXh1g==)
at #=qMIpsXBuH0t9rbeNBcCB77DuZHumrogCBIzxKX$tKhuLKBiHXV0GZ1TYfSJEQOrab.#=qpGdbZ0k1O7jLPIO4j1ujLA==(String #=qK6K$plNan4$vOBY35UxNoA==)
Then I seem to be the only one with this issue. I forgot about it when posting, but I think I've mentioned it before.peppy wrote:
it appears fine here, albeit after the update process.
[05:44] <VeilStar> Oh by the way... is that recovery/settings/repair dialog when holding shift and opening osu! supposed to be fixed? Because it's not working on my end, while everyone else says it does. Any idea?
[05:44] <smoogipooo> o.O it is supposed to be fixed yes
Sorry, missed that for a little while.TicClick wrote:
And no, VeilStar, this also happens on public builds since I don't know when, probably since in-game changelog implementation.
b20150506.3cuttingedge and still occasionally getting said corruption. All you need to do is keep osu! minimized for a while, and either the name of a user who's first to post in chat after you restore the window, or (mostly) the title and artist of the song currently playing turn into blocks:Tom94 wrote:
Please let us know if you can still trigger texture corruption (blocky sprites) after this change.
not sure if chat counts but can confirm still happening on usernames and other messages.TicClick wrote:
b20150506.3cuttingedge and still occasionally getting said corruption. All you need to do is keep osu! minimized for a while, and either the name of a user who's first to post in chat after you restore the window, or (mostly) the title and artist of the song currently playing turn into blocks:Tom94 wrote:
Please let us know if you can still trigger texture corruption (blocky sprites) after this change.
sometimes it's a random string from one of recent game screens (for ex., osu! once took someone's performance value with "Performance: " and used it instead of solid block twice on the same line, fiirst instead of timestamp and then instead of my own nickname in chat)
Can confirm fixed as of b20150507ceBanchoBot wrote:
Issue(s) in this thread have been addressed by the following changes:The changes will be applied to builds newer than b20150506.4cuttingedge.
- Fix triangles drawing but not disposing when minimised (causing massive lag/cpu usage). (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.
Never crashed here. Post a crash log?Shizuyi wrote:
I still have some performance issues + osu chrashes more often.
Don't worry, your issue is actually valid (and fixed soon) even though it doesn't happen while spectating. The menus should also be able to run at an arbitrary frame rate if so desired.Trosk- wrote:
Problem Details: On the tournament client, the osu windows lock at 30 fps if you don't click at them, and you only can have one running at 60 fps, the other ones run at 30.
On the video look at the fps counter whn i click on the windows (forgot to record the cursor, sorry -.-)
Video or screenshot showing the problem: https://www.youtube.com/watch?v=FqiaihIpxHQ
osu! version: 20150508.5cuttingedge
You can delete this post if needed. It's fixed, and it was a double post, i'm sorry..
Don't worry, your issue is actually valid (and fixed soon) even though it doesn't happen while spectating. The menus should also be able to run at an arbitrary frame rate if so desired.Thank you ^^
...whoa. Confirmed as of b20150508.5ce.Z e r s s wrote:
Hey !
I'm always playing with cutting edge, and I wanted to play with flashlight, and... I was seeing the whole map. Nothing changed.
I think it's a cutting edge bug, I don't know ^^
Bye !
No, it's corrected, thanks !Tom94 wrote:
Anyone still having issues with FlashLight not working correctly? Should be fixed now.
peppy wrote:
please update to the latest build and check for an error.txt in your skin folder after attempting to load it.
None of my skins work either in the latest cutting edge as of posting this (osu!cuttingedge b20150509). I tried about 10 different skins and i got the same error message ''Error while loading current skin's configuration file (skin.ini). Please check and correct any errors''. I did as peppy instructed and checked my skin folder after getting the error message, here is the code found in the error.txt:Shizuku- wrote:
Here goes:System.MissingMethodException: Method not found: 'Int32 System.Environment.get_CurrentManagedThreadId()'.
at #=qSE2myK38WFeUnS$I_ErmW1GSvY6S5dPQazK9A6jnVmkdpDZv2ypDuz_x7l2gXupT.#=qFgRk_vYkSlqfuPwFbLyO8SJY1BwKpOi7h_vFN9A2ers=..ctor(Int32 #=qNHTfHZo$Nmx$TazbGr9M9g==)
at #=qoVb1NirFIJvP_q0SCJvDHZxdthrNzpPG58EUSvq$HfI=.#=qZEfZFV69xxUVDwJk9q6NkQ==[T]()
at #=qS6_4R5k6pyioZEIEUBCrLeRk9NEQmt9cyj8Bh4V9qw8=.#=qunxcNqQq4qw01cZ0WKXWDA==()
at #=qoVb1NirFIJvP_q0SCJvDHZxdthrNzpPG58EUSvq$HfI=.#=q0AJdn6R1euYTDTUw3Ck98w==(String #=qszTF18FWf8i6AOUSHeXh1g==)
at #=qMIpsXBuH0t9rbeNBcCB77DuZHumrogCBIzxKX$tKhuLKBiHXV0GZ1TYfSJEQOrab.#=qpGdbZ0k1O7jLPIO4j1ujLA==(String #=qK6K$plNan4$vOBY35UxNoA==)
System.MissingMethodException: Method not found: 'Int32 System.Environment.get_CurrentManagedThreadId()'.
at #=qSJyZ$DVSxUDjN642mYm8ElS3UfhCi3yCMD4aXk6srkZVWclBFSJN_LMwy1Ese4TB.#=quIArIigiAtpuugrqBofzeYPzbncbM0EPkbuAucT7Kpc=..ctor(Int32 #=qWhS9fyrLr6sVi1MOXCYQxg==)
at #=qKDi7EJTeEVOF8qmoQ4hTxuG$2cJXkdDE4S_eVYpZwcU=.#=qDWYqZNO2eVMtXbXjauCT_g==[T]()
at #=qVkIbIcuRid79pvE0n85_sHZP_dVI8dXMGjCnmUfjs1c=.#=qEVx2E1mktDqxH2M$5$m_4g==()
at #=qKDi7EJTeEVOF8qmoQ4hTxuG$2cJXkdDE4S_eVYpZwcU=.#=qOgrn7YAnncUmJGnD9oQ4og==(String #=qEtHovLZr$u1VUYCKehIW9A==)
at #=qapxkTdytZxlReBTLTzmZ7SEkmQ7LrSFXJl07MtwySjuMcU8MfZTkh3M$mWjI2cTv.#=qZ9CTuY5ZfwPElep6nESQAQ==(String #=q$IsWZCElPAXpdZopQUTOag==)
Correct me if I'm wrong (with more details about the issue,) but this isn't cutting-edge specific?Default wrote:
The game crashed after trying to play a map I had just saved, it just kept loading forever and I wasn't able to close it.
I forgot to say that I tried making a new diff with no inherited timing points and it still happened until I closed the game (not just the editor but the game itself).VeilStar wrote:
This usually happens if you have an inherited (green) timing point before an uninherited (red) one. So check for that?