Gotta get in on that osu!nightly.
forum
osu!test now more usable m5d48
posted
Total Posts
62
The test build is always up-to-date with the changelog. There are also some half-baked features in there (replay seeking, emoji) which aren't ready for public yet.
At the moment the test build is 99% in sync with public, but this isn't the case when there hasn't been a public release for 1 week or more. You will be able to view and play with new features as they are added, and watch the game develop on a daily basis.
There are usually 0~5 test build patches a day, for reference.
At the moment the test build is 99% in sync with public, but this isn't the case when there hasn't been a public release for 1 week or more. You will be able to view and play with new features as they are added, and watch the game develop on a daily basis.
There are usually 0~5 test build patches a day, for reference.
Marcooo_old
You should definitely make something either in the client or on the site that's like a report form, so people don't have to create a thread on a public forum for everyone to see. Since, you know, it doesn't necessarily encourage people to report bugs if they have to fill out an entire forum thread if you ask me. At least that's what it's like to me.
Sweet! I'll be using the test build more often then 
Although I wish there was an option to unify the public build's collections with the test build's collections, but seeing as they're just .db files it shouldn't be difficult to move them back and forth manually
EDIT: Also, the watermark seems to be in the way of the hit error meter. Not really that big of a deal though.
Although I wish there was an option to unify the public build's collections with the test build's collections, but seeing as they're just .db files it shouldn't be difficult to move them back and forth manually
EDIT: Also, the watermark seems to be in the way of the hit error meter. Not really that big of a deal though.
I second this, osu! Test build should have a extra option so u can report right from inside the client or maybe a special channel were all people do is post things they found maybe?Marcooo wrote: 506f2i
You should definitely make something either in the client or on the site that's like a report form, so people don't have to create a thread on a public forum for everyone to see. Since, you know, it doesn't necessarily encourage people to report bugs if they have to fill out an entire forum thread if you ask me. At least that's what it's like to me.
And how do you then keep track of them, by searching through logs?.. seriously D:?jackishere wrote: 1i6x32
I second this, osu! Test build should have a extra option so u can report right from inside the client or maybe a special channel were all people do is post things they found maybe?Marcooo wrote: 506f2i
You should definitely make something either in the client or on the site that's like a report form, so people don't have to create a thread on a public forum for everyone to see. Since, you know, it doesn't necessarily encourage people to report bugs if they have to fill out an entire forum thread if you ask me. At least that's what it's like to me.
Marcooo_old
Make a simple web form that mails the reports to the technical team or something like thatMarcin wrote: 1u1j
And how do you then keep track of them, by searching through logs?.. seriously D:?
Edit: Maybe a mail for like [email protected] and give the osu! team access to it and delete the reports you've looked into?
There's nothing wrong with having to make a forum thread, it doesn't even have to be very lengthy. The only thing you need to put in your post really is how to reproduce the bug (and screenshots, but those aren't entirely necessary if your repro steps are easy to follow).Marcooo wrote: 506f2i
You should definitely make something either in the client or on the site that's like a report form, so people don't have to create a thread on a public forum for everyone to see. Since, you know, it doesn't necessarily encourage people to report bugs if they have to fill out an entire forum thread if you ask me. At least that's what it's like to me.
And the main reason for the bugs/tech forum being public is so others can test and confirm that it's a bug.
If there are changes made which would break maps, BSS will be disabled in the test build. As long as you can submit, it should be fine to do so.TheVileOne wrote: p102h
I'm curious whether I can safely map in the test build. I know that before, the test build would create test build only files. What will happen if I make changes to a beatmap and submit them from the test build?
I'd like the option to remove the text overlay denoting if a is using the test build. It does not work well with the score meter:
We currently have 4 locations which show we are using osu!test - the text overlay, the image overlay, the text bar on top of the osu! circle (http://u.nyaa.asia/agy.png) and text in top right of options.
Apart from this, I'm up for using osu!test.
Edit: Fixed as soon as I posted it :3
We currently have 4 locations which show we are using osu!test - the text overlay, the image overlay, the text bar on top of the osu! circle (http://u.nyaa.asia/agy.png) and text in top right of options.
Apart from this, I'm up for using osu!test.
Edit: Fixed as soon as I posted it :3
Somehow, I can't the test build, even though I've never ed it before. osu!test.exe doesn't show up in my folder...
I there was something in the technical forums about this problem, but I can't find it anymore
I there was something in the technical forums about this problem, but I can't find it anymore
5 <- post there then
! nice
After the update just now, osu continues to crash whenever i start a song. Help D:
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.String.Concat(String str0, String str1)
at #on.#On.#ceb()
at #on.#On.#99()
at #Wo.#Xo.#Ls()
at #Yc.#4c.#rt()
at #Yc.#4c.#Ct(Object , EventArgs )
at #Yc.#8c.#Zt()
at #Yc.#nd.#dw(Object , EventArgs )
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(Int32 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 #Yc.#nd.#It()
at #Yc.#4c.#It()
at #Wo.#Vo.#0qb(String , Boolean )
at System.String.Concat(String str0, String str1)
at #on.#On.#ceb()
at #on.#On.#99()
at #Wo.#Xo.#Ls()
at #Yc.#4c.#rt()
at #Yc.#4c.#Ct(Object , EventArgs )
at #Yc.#8c.#Zt()
at #Yc.#nd.#dw(Object , EventArgs )
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(Int32 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 #Yc.#nd.#It()
at #Yc.#4c.#It()
at #Wo.#Vo.#0qb(String , Boolean )
Please report any issues in tech posting.php?mode=post&f=5
Hmm, I like the update, but don't really feel too great about it being er-only...
I like testing pre-release programs and games and giving , but why should I have to essentially pay to do this (I know it's technically "donating", but if my only intent is to test new features and give ...)? I like donating to projects that I find are pretty awesome; osu! was actually the first game I donated to without caring about any of the er features. Just hate feeling like I "have" to donate (or essentially pay is the way I look at it) to do something, especially something like testing pre-release software.
Just the way I feel about donations I guess. Can't non-s just be able to use the test client, but not have score updating? Or maybe use the system that existed before where you could make a 3-hour (or so) temporary for the test client?
I like testing pre-release programs and games and giving , but why should I have to essentially pay to do this (I know it's technically "donating", but if my only intent is to test new features and give ...)? I like donating to projects that I find are pretty awesome; osu! was actually the first game I donated to without caring about any of the er features. Just hate feeling like I "have" to donate (or essentially pay is the way I look at it) to do something, especially something like testing pre-release software.
Just the way I feel about donations I guess. Can't non-s just be able to use the test client, but not have score updating? Or maybe use the system that existed before where you could make a 3-hour (or so) temporary for the test client?