///
forum
[Archived] Issues with Latest Cutting-edge Build (Post Here) 5z1i67
posted
Total Posts
2,521
All the beatmaps from my Collections list are gone in the latest update :L
http://s23.postimg.org/xganh2zuh/screenshot004.jpg
http://s23.postimg.org/xganh2zuh/screenshot004.jpg
With lastest 20141202 build, combo burst sound doesnt play
I Read the update description multiple times, but ppy didnt mention anything about disabling combo bursts (removing combo burst sounds would be dumb anyhow) so I am assuming it is a bug. The cutting edge build before this latest one didnt have such problem either.
Basically, my skin with custom combo burst sounds:
DOESNT PLAY on cutting edge
PLAYS no prob on stable
** The combo burst images appears without any problem. It is just the sound**
This happens in all Mods
I Read the update description multiple times, but ppy didnt mention anything about disabling combo bursts (removing combo burst sounds would be dumb anyhow) so I am assuming it is a bug. The cutting edge build before this latest one didnt have such problem either.
Basically, my skin with custom combo burst sounds:
DOESNT PLAY on cutting edge
PLAYS no prob on stable
** The combo burst images appears without any problem. It is just the sound**
This happens in all Mods
I noticed in 20141202, when I switch languages, the back button in the options menu doesn't change in accordance to the language chosen.
Sorry for the potato quality.
Sorry for the potato quality.
[Yong] wrote: 1f6x71
With lastest 20141202 build, combo burst sound doesnt play
I Read the update description multiple times, but ppy didnt mention anything about disabling combo bursts (removing combo burst sounds would be dumb anyhow) so I am assuming it is a bug. The cutting edge build before this latest one didnt have such problem either.
Basically, my skin with custom combo burst sounds:
DOESNT PLAY on cutting edge
PLAYS no prob on stable
** The combo burst images appears without any problem. It is just the sound**
This happens in all Mods
FIXED b20141203
Thank you!
There is no host t/256935
IA42
IA42
dunno with other issue but my issue seems fixed now \:D/IA42 wrote: 1n6445
I dunno why but my Skin.ini seems error now
- first "Version: latest" no longer available
- then i tried change to new version "Version: 2.4" but it's always make new line of "Hitcircleoverlayabovenumber" when change skin and "menuglow, keys, key(num)" line when change mania key
Send over your skin.iniReddScorn wrote: 686i2v
on skins only using 2 combo colours only, the third and fourth combo colours from the default scheme are used.
that breaks skins focused on a single colour and should be reverted back to at least having 2 colours defined. I just don't see the reason for that change.
Again what simply happened: I only have two colours defined and osu! added Combo3 and Combo4 from default skin.drum drum wrote: 215943
Send over your skin.ini
skin.ini
[General]
Name:
Author: ReddScorn
Version: latest
CursorExpand: 1
CursorRotate: 0
CursorTrailRotate: 0
AllowSliderBallTint: 0
SpinnerFadePlayfield: 0
SpinnerNoBlink: 1
HitCircleOverlayAboveNumber: 0
[Colours]
Combo1: 255,255,255
Combo2: 255,255,255
SliderBorder: 255,255,255
SliderTrackOverride: 0,0,0
SongSelectActiveText: 255,255,255
SongSelectInactiveText: 120,120,120
[Fonts]
HitCirclePrefix: default
HitCircleOverlap: 40
ScorePrefix: score
ScoreOverlap: 3
ComboPrefix: score
ComboOverlap: 3
This issue has been addressed by the following change by peppy:
Fix combo colours being read incorrectly.
It will be applied to builds newer than b20141208cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Fix combo colours being read incorrectly.
It will be applied to builds newer than b20141208cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
This issue has been addressed by the following change by smoogipooo:
Fix mania skin migrations missing a column line.
It will be applied to builds newer than b20141208cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Fix mania skin migrations missing a column line.
It will be applied to builds newer than b20141208cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
This issue has been addressed by the following change by smoogipooo:
Fix mania skin migrations not migrating ColumnWidth.
It will be applied to builds newer than b20141208cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Fix mania skin migrations not migrating ColumnWidth.
It will be applied to builds newer than b20141208cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
In the osu! folder, open with notepad the file osu!.<Windows name>.cfg, search for the line "Skin = <Skin Name>" and delete it, then save the file.Al3xeo wrote: 2d1j4y
For my osu i launched it in cutting edge mode and now i cannot do anything. The cursor does not display and keyboard buttons do not work at all. Please assist or fix thanks
Due to this i cannot change back to stable mode in the game and i do not know how out to change outside of the game.
Full Tablet wrote: 5o4t51
In the osu! folder, open with notepad the file osu!.<Windows name>.cfg, search for the line "Skin = <Skin Name>" and delete it, then save the file.Al3xeo wrote: 2d1j4y
For my osu i launched it in cutting edge mode and now i cannot do anything. The cursor does not display and keyboard buttons do not work at all. Please assist or fix thanks
Due to this i cannot change back to stable mode in the game and i do not know how out to change outside of the game.
This fixed it thank you.
This issue has been addressed by the following change by smoogipooo:
Fix interface not hiding with Shift+Tab.
It will be applied to builds newer than b20141209.2cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Fix interface not hiding with Shift+Tab.
It will be applied to builds newer than b20141209.2cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Another issue regarding colours.
Dec 5, 2014
was later changed to RGBA.
It made me think that you could finally use transparent hitcircles without making it manually in a software like GIMP or PS, but that's not fully working.
When using RGBA on normal Combo colours (not on the mania colours) some weird behaviour happens.
The hitcircle on circles alone is at first solid but the transparency changes midway to the set value and on sliders it already is transparent.
Another thing is when using very low transparency values, it makes the approachcircle practically invisible.
As you can see the slider uses the transparency fully, the first circle about to be clicked is transparent, the second circle is still solid (only appears a bit transparent due to fading in), and the approachcircles are transparent. I used default hitcircle and approachcircle here.
Last thing is when using the transparency value = 0, the colours won't be applied and the game crashes when the first slider of a map gets rendered.
tl;dr using RGBA code on normal/non-mania combo colours it makes approach invisible and can crash the game at R=x,G=y,B=z,A=0.
Dec 5, 2014
was later changed to RGBA.
It made me think that you could finally use transparent hitcircles without making it manually in a software like GIMP or PS, but that's not fully working.
When using RGBA on normal Combo colours (not on the mania colours) some weird behaviour happens.
The hitcircle on circles alone is at first solid but the transparency changes midway to the set value and on sliders it already is transparent.
Another thing is when using very low transparency values, it makes the approachcircle practically invisible.
As you can see the slider uses the transparency fully, the first circle about to be clicked is transparent, the second circle is still solid (only appears a bit transparent due to fading in), and the approachcircles are transparent. I used default hitcircle and approachcircle here.
skin.ini for transparency problems
[General]
Name:
Author: ReddScorn
Version: latest
CursorExpand: 1
CursorRotate: 0
CursorTrailRotate: 0
AllowSliderBallTint: 0
SpinnerFadePlayfield: 0
SpinnerNoBlink: 1
HitCircleOverlayAboveNumber: 0
[Colours]
Combo1: 255,255,85,20
Combo2: 96,255,68,20
Combo3: 0,128,255,20
Combo4: 255,68,68,20
SliderBorder: 255,255,255
SliderTrackOverride: 0,0,0
SongSelectActiveText: 255,255,255
SongSelectInactiveText: 120,120,120
Last thing is when using the transparency value = 0, the colours won't be applied and the game crashes when the first slider of a map gets rendered.
skin.ini for crash validation
[General]
Name:
Author: ReddScorn
Version: latest
CursorExpand: 1
CursorRotate: 0
CursorTrailRotate: 0
AllowSliderBallTint: 0
SpinnerFadePlayfield: 0
SpinnerNoBlink: 1
HitCircleOverlayAboveNumber: 0
[Colours]
Combo1: 255,255,85,0
Combo2: 96,255,68,0
Combo3: 0,128,255,0
Combo4: 255,68,68,0
SliderBorder: 255,255,255
SliderTrackOverride: 0,0,0
SongSelectActiveText: 255,255,255
SongSelectInactiveText: 120,120,120
tl;dr using RGBA code on normal/non-mania combo colours it makes approach invisible and can crash the game at R=x,G=y,B=z,A=0.
This issue has been addressed by the following change by smoogipooo:
Disable transparent colours for non-mania skins.
It will be applied to builds newer than b20141210cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Disable transparent colours for non-mania skins.
It will be applied to builds newer than b20141210cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
This issue has been addressed by the following change by smoogipooo:
Fix incorrect scaling leading to premature score screen sprite disappearance.
It will be applied to builds newer than b20141211.1cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Fix incorrect scaling leading to premature score screen sprite disappearance.
It will be applied to builds newer than b20141211.1cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
This issue has been addressed by the following change by Damnae:
Fix editor not saving / deleting beatmap backgrounds.
It will be applied to builds newer than b20141211.2cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Fix editor not saving / deleting beatmap backgrounds.
It will be applied to builds newer than b20141211.2cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
This issue has been addressed by the following change by Damnae:
Fix beatmap backgrounds not loading in some cases.
It will be applied to builds newer than b20141211.2cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Fix beatmap backgrounds not loading in some cases.
It will be applied to builds newer than b20141211.2cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
This issue has been addressed by the following change by peppy:
Fix line drawing in opengl.
It will be applied to builds newer than b20141211.11cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Fix line drawing in opengl.
It will be applied to builds newer than b20141211.11cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
If you change your Resolution in OSU! (Could only test with non-Widescreen options due to not being able to scroll down the list of options) that Options glitch happens (for me because idk if other people have confirmed this on their OSU!) (Could only test in DirectX because of the problem that I'm having below)
Problem Example Video for Options Glitch (Sorry for the sloppyness XD):
http://puu.sh/dqWa7.mp4
- - - - - - - - - - - - - - - - - - - - - - - - - -
OpenGL is completely broke for me... (Just updated to the newest Cutting Edge of 12-12-14 (OSU! Time... Because it is 12-11-14 for me); With "Fix Line Drawing in OpenGL" as the newest recent change)
The screen is entirely Black when I start up, except occasionally when I start OSU! I get either a Red Profile "Banner" (I guess you call it that...) with a Black screen and/or the "Welcome" screen frozen on there...
Happens in ALL resolutions (So I didn't test with any other Res. than the lowest one because that would take a long time XD) and all FPS settings (I did Unlimited, 60 V-Sync, and 120) (I changed them from the amazing Opening OSU! + Shift feature...)... If I stop the song that is playing (From the "C" key) and click and go by ear of where Solo is, I enter Song Select where it will just display (Sometimes) a image of song select (OSU! can't enter edit mode... It just hangs as one part in my video shows); Nothing else... And If I press ESC. and go back to menu it's still completely Black... OpenGL is sadly 100% unusable...
Problem Example Video (Sorry for the sloppyness XD):
http://puu.sh/dqVtI.mp4
Problem Example Video for Options Glitch (Sorry for the sloppyness XD):
http://puu.sh/dqWa7.mp4
- - - - - - - - - - - - - - - - - - - - - - - - - -
OpenGL is completely broke for me... (Just updated to the newest Cutting Edge of 12-12-14 (OSU! Time... Because it is 12-11-14 for me); With "Fix Line Drawing in OpenGL" as the newest recent change)
The screen is entirely Black when I start up, except occasionally when I start OSU! I get either a Red Profile "Banner" (I guess you call it that...) with a Black screen and/or the "Welcome" screen frozen on there...
Happens in ALL resolutions (So I didn't test with any other Res. than the lowest one because that would take a long time XD) and all FPS settings (I did Unlimited, 60 V-Sync, and 120) (I changed them from the amazing Opening OSU! + Shift feature...)... If I stop the song that is playing (From the "C" key) and click and go by ear of where Solo is, I enter Song Select where it will just display (Sometimes) a image of song select (OSU! can't enter edit mode... It just hangs as one part in my video shows); Nothing else... And If I press ESC. and go back to menu it's still completely Black... OpenGL is sadly 100% unusable...
Problem Example Video (Sorry for the sloppyness XD):
http://puu.sh/dqVtI.mp4
This issue has been addressed by the following change by peppy:
Fix options categories breaking on changing resolution.
It will be applied to builds newer than b20141211.12cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Fix options categories breaking on changing resolution.
It will be applied to builds newer than b20141211.12cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Sadly no... 
Same issues almost... Getting a White Rectangle where the "Banner" is for my Profile now... Really only difference
Edit: Randomly opened Solo and picked a song... My computer froze SUPER hard (Didn't display anything except the DirectX loading circle, with the map BG, and my last cursor movement in a still image)... Only about 250,000k memory though... Pretty normal... Idk what happened
Same issues almost... Getting a White Rectangle where the "Banner" is for my Profile now... Really only difference
Edit: Randomly opened Solo and picked a song... My computer froze SUPER hard (Didn't display anything except the DirectX loading circle, with the map BG, and my last cursor movement in a still image)... Only about 250,000k memory though... Pretty normal... Idk what happened
I'll try my hardest... But my computer will most likely crash... So give me a little bit lol (The lag is super bad... I really have no idea what it is :/)
Edit: I just got another Update for OSU!... The Menu now loads but Song Select is bugged still for me...
If I go to Solo > Song Select it's fine... Until I click on anything... Then it does the same thing it's been doing...
Edit: I just got another Update for OSU!... The Menu now loads but Song Select is bugged still for me...
If I go to Solo > Song Select it's fine... Until I click on anything... Then it does the same thing it's been doing...
Super close... OSU! now starts but it's doing this now... (Also happens in Edit Mode... Just Tested it)
(OSU! just failed to start on my 3rd restart after testing it in the video and edit mode just now... Will not start anymore... Pretty weird :/)
lol... So I selected a random song... And I can play it... Song Select just appears to be broken (Only once... After the one random song it breaks again...)
If It helps any at all... I use .NET Framework 4.6 Preview, Graphics Compatibility, and Computer Spec's
Problem Example:
http://puu.sh/drcZy.mp4
Updated:
http://puu.sh/drdTQ.mp4
(OSU! just failed to start on my 3rd restart after testing it in the video and edit mode just now... Will not start anymore... Pretty weird :/)
lol... So I selected a random song... And I can play it... Song Select just appears to be broken
(Only once... After the one random song it breaks again...)If It helps any at all... I use .NET Framework 4.6 Preview, Graphics Compatibility, and Computer Spec's
Problem Example:
Updated:
http://puu.sh/drdTQ.mp4
On the current CuttingEdge build I get "error while loading skin.ini" message on each skin reload (CTRL-ALT-SHIFT-S) and restarting osu! every time. It's a mystery that my current skin.ini can be read in the Stable release but not on the current CuttingEdge version (previous version before the Christmas update was working). Is it just me or osu! misintepreting the skin.ini components, or otherwise?
I tried to remove all of the skin.ini contents except the name and author. After saving and reloading in the CuttingEdge build, the message still displays.
I tried to remove all of the skin.ini contents except the name and author. After saving and reloading in the CuttingEdge build, the message still displays.
Everything is working as it should
except the Pie Chart like Timer during play (Only when it counts in the time before the map starts...)
(Fixed below...)
Restarted OSU! a couple times, went to solo and played around in Song Select, Play a couple songs, then with mods, then went to Edit mode, Started to edit a song, and changed my Res. and FPS and tested and it's working fine... Haven't tested Multi. but I'm sure that it's fine...
Thanks you for the quick fix
(Fixed below...)
Restarted OSU! a couple times, went to solo and played around in Song Select, Play a couple songs, then with mods, then went to Edit mode, Started to edit a song, and changed my Res. and FPS and tested and it's working fine... Haven't tested Multi. but I'm sure that it's fine...
Thanks you for the quick fix
I actually included the skin.ini within my skin folder. There was nothing wrong on the Stable release but never on the CuttingEdge version (after the Christmas update).peppy wrote: 73101g
You say this but you don't include your skin.ini?
skin.ini's Contents
[General]
Name: Skylanders 2
Author: Garygoh884
SliderBallFlip: 1
CursorRotate: 0
CursorExpand: 0
CursorCentre: 1
SliderBallFrames: 1
HitCircleOverlayAboveNumber: 0
SliderStyle: 2
SpinnerNoBlink: 1
SpinnerFadePlayfield: 0
Version: 2.2
[Colours]
Combo1: 241,199,12
Combo2: 241,58,12
Combo3: 241,157,12
Combo4: 241,96,12
SliderBorder: 255,168,31
SliderTrackOverride: 86,86,86
SongSelectActiveText: 255,255,255
StarBreakAdditive: 255,170,0
[Fonts]
HitCirclePrefix: basefont
HitCircleOverlap: 6
ScorePrefix: basefont
ScoreOverlap: 6
[Mania]
Keys: 10
//Mania skin config
ColumnStart: 40
HitPosition: 413
SpecialStyle: 1
SpecialPositionLeft: 1
UpsideDown: 0
JudgementLine: 0
ScorePosition: 999
ComboPosition: 999
FontCombo: basefont
LightFramePerSecond: 6
ColumnWidth: 24,20,19,20,19,20,19,20,19,20
//Colours
Colour1: 0,0,0,255
Colour2: 0,0,0,255
Colour3: 0,0,0,255
Colour4: 0,0,0,255
Colour5: 0,0,0,255
Colour6: 0,0,0,255
Colour7: 0,0,0,255
Colour8: 0,0,0,255
Colour9: 0,0,0,255
Colour10: 0,0,0,255
ColourLight1: 156,156,156,255
ColourLight2: 112,153,92,255
ColourLight3: 61,102,41,255
ColourLight4: 112,153,92,255
ColourLight5: 61,102,41,255
ColourLight6: 112,153,92,255
ColourLight7: 61,102,41,255
ColourLight8: 112,153,92,255
ColourLight9: 61,102,41,255
ColourLight10: 112,153,92,255
ColourHold: 255,255,255,255
ColourBreak: 120,0,0,0
//images
KeyImage0: mania-keyX
KeyImage0D: mania-keyXD
KeyImage5: mania-keyS
KeyImage5D: mania-keySD
NoteImage0: mania-noteX
NoteImage0L: mania-noteXL
NoteImage0H: mania-noteXH
NoteImage5: mania-noteS
NoteImage5L: mania-noteSL
NoteImage5H: mania-noteSH
ColumnLineWidth: 0,0,0,0,0,0,0,0,0,0,0
BarlineHeight: 1
[Mania]
Keys: 1
//Mania skin config
ColumnStart: 40
HitPosition: 413
SpecialStyle: 1
SpecialPositionLeft: 1
UpsideDown: 0
JudgementLine: 0
ScorePosition: 999
ComboPosition: 999
FontCombo: basefont
LightFramePerSecond: 6
ColumnWidth: 50,50,50,50
//Colours
Colour1: 0,0,0,255
Colour2: 0,0,0,255
Colour3: 0,0,0,255
Colour4: 0,0,0,255
ColourLight1: 112,153,92,140
ColourLight2: 0,0,0,0
ColourLight3: 0,0,0,0
ColourLight4: 0,0,0,0
ColourBreak: 120,0,0,0
KeyImage2: mania-keyN
KeyImage2D: mania-keyN
KeyImage3: mania-keyN
KeyImage3D: mania-keyN
KeyImage4: mania-keyN
KeyImage4D: mania-keyN
ColumnLineWidth: 0,0,0,0,0
BarlineHeight: 1
[Mania]
Keys: 2
//Mania skin config
ColumnStart: 40
HitPosition: 413
SpecialStyle: 1
SpecialPositionLeft: 1
UpsideDown: 0
JudgementLine: 0
ScorePosition: 999
ComboPosition: 999
FontCombo: basefont
LightFramePerSecond: 6
ColumnWidth: 50,50,50,50
//Colours
Colour1: 0,0,0,255
Colour2: 0,0,0,255
Colour3: 0,0,0,255
Colour4: 0,0,0,255
ColourLight1: 112,153,92,140
ColourLight2: 112,153,92,140
ColourLight3: 0,0,0,0
ColourLight4: 0,0,0,0
ColourBreak: 120,0,0,0
KeyImage3: mania-keyN
KeyImage3D: mania-keyN
KeyImage4: mania-keyN
KeyImage4D: mania-keyN
ColumnLineWidth: 0,0,0,0,0
BarlineHeight: 1
[Mania]
Keys: 3
//Mania skin config
ColumnStart: 40
HitPosition: 413
SpecialStyle: 1
SpecialPositionLeft: 1
UpsideDown: 0
JudgementLine: 0
ScorePosition: 999
ComboPosition: 999
FontCombo: basefont
LightFramePerSecond: 6
ColumnWidth: 50,50,50,50
//Colours
Colour1: 0,0,0,255
Colour2: 0,0,0,255
Colour3: 0,0,0,255
Colour4: 0,0,0,255
ColourLight1: 112,153,92,140
ColourLight2: 61,102,41,140
ColourLight3: 112,153,92,140
ColourLight4: 0,0,0,0
ColourBreak: 120,0,0,0
KeyImage4: mania-keyN
KeyImage4D: mania-keyN
ColumnLineWidth: 0,0,0,0,0
BarlineHeight: 1
[Mania]
Keys: 4
//Mania skin config
ColumnStart: 40
HitPosition: 413
SpecialStyle: 1
SpecialPositionLeft: 1
UpsideDown: 0
JudgementLine: 0
ScorePosition: 999
ComboPosition: 999
FontCombo: basefont
LightFramePerSecond: 6
ColumnWidth: 50,50,50,50
//Colours
Colour1: 0,0,0,255
Colour2: 0,0,0,255
Colour3: 0,0,0,255
Colour4: 0,0,0,255
ColourLight1: 112,153,92,140
ColourLight2: 61,102,41,140
ColourLight3: 61,102,41,140
ColourLight4: 112,153,92,140
ColourBreak: 120,0,0,0
ColumnLineWidth: 0,0,0,0,0
BarlineHeight: 1
[Mania]
Keys: 5
//Mania skin config
ColumnStart: 40
HitPosition: 413
SpecialStyle: 0
SpecialPositionLeft: 1
UpsideDown: 0
JudgementLine: 0
ScorePosition: 999
ComboPosition: 999
FontCombo: basefont
LightFramePerSecond: 6
ColumnWidth: 40,40,40,40,40
//Colours
Colour1: 0,0,0,255
Colour2: 0,0,0,255
Colour3: 0,0,0,255
Colour4: 0,0,0,255
Colour5: 0,0,0,255
ColourLight1: 112,153,92,140
ColourLight2: 61,102,41,140
ColourLight3: 112,153,92,140
ColourLight4: 61,102,41,140
ColourLight5: 112,153,92,140
ColourBreak: 120,0,0,255
ColumnLineWidth: 0,0,0,0,0,0
BarlineHeight: 1
[Mania]
Keys: 6
//Mania skin config
ColumnStart: 40
HitPosition: 413
SpecialStyle: 0
SpecialPositionLeft: 1
UpsideDown: 0
JudgementLine: 0
ScorePosition: 999
ComboPosition: 999
FontCombo: basefont
LightFramePerSecond: 6
ColumnWidth: 33,34,33,33,34,33
//Colours
Colour1: 0,0,0,255
Colour2: 0,0,0,255
Colour3: 0,0,0,255
Colour4: 0,0,0,255
Colour5: 0,0,0,255
Colour6: 0,0,0,255
ColourLight1: 112,153,92,140
ColourLight2: 61,102,41,140
ColourLight3: 112,153,92,140
ColourLight4: 112,153,92,140
ColourLight5: 61,102,41,140
ColourLight6: 112,153,92,140
ColourHold: 255,255,255,255
ColourBreak: 120,0,0,0
ColumnLineWidth: 0,0,0,0,0,0,0
BarlineHeight: 1
[Mania]
Keys: 7
//Mania skin config
ColumnStart: 40
HitPosition: 413
SpecialStyle: 0
SpecialPositionLeft: 1
UpsideDown: 0
JudgementLine: 0
//345,279
ScorePosition: 999
ComboPosition: 999
//280,264
FontCombo: basefont
LightFramePerSecond: 6
ColumnWidth: 28,29,28,30,28,29,28
//Colours
Colour1: 0,0,0,255
Colour2: 0,0,0,255
Colour3: 0,0,0,255
Colour4: 0,0,0,255
Colour5: 0,0,0,255
Colour6: 0,0,0,255
Colour7: 0,0,0,255
ColourLight1: 112,153,92,140
ColourLight2: 61,102,41,140
ColourLight3: 112,153,92,140
ColourLight4: 61,102,41,140
ColourLight5: 112,153,92,140
ColourLight6: 61,102,41,140
ColourLight7: 112,153,92,140
ColourHold: 255,255,255,255
ColourBreak: 120,0,0,0
ColumnLineWidth: 0,0,0,0,0,0,0,0
BarlineHeight: 1
[Mania]
Keys: 8
//Mania skin config
ColumnStart: 40
HitPosition: 413
SpecialStyle: 1
SpecialPositionLeft: 1
UpsideDown: 0
JudgementLine: 0
ScorePosition: 999
ComboPosition: 999
FontCombo: basefont
LightFramePerSecond: 6
ColumnWidth: 28,25,24,25,24,25,24,25
//Colours
Colour1: 0,0,0,255
Colour2: 0,0,0,255
Colour3: 0,0,0,255
Colour4: 0,0,0,255
Colour5: 0,0,0,255
Colour6: 0,0,0,255
Colour7: 0,0,0,255
Colour8: 0,0,0,255
ColourLight1: 156,156,156,255
ColourLight2: 112,153,92,255
ColourLight3: 61,102,41,255
ColourLight4: 112,153,92,255
ColourLight5: 61,102,41,255
ColourLight6: 112,153,92,255
ColourLight7: 61,102,41,255
ColourLight8: 112,153,92,255
ColourHold: 255,255,255,255
ColourBreak: 120,0,0,0
//images
KeyImage0: mania-keyX
KeyImage0D: mania-keyXD
KeyImage4: mania-keyS
KeyImage4D: mania-keySD
NoteImage0: mania-noteX
NoteImage0L: mania-noteXL
NoteImage0H: mania-noteXH
NoteImage4: mania-noteS
NoteImage4L: mania-noteSL
NoteImage4H: mania-noteSH
ColumnLineWidth: 0,0,0,0,0,0,0,0,0
BarlineHeight: 1
[Mania]
Keys: 9
//Mania skin config
ColumnStart: 40
HitPosition: 413
SpecialStyle: 0
SpecialPositionLeft: 0
UpsideDown: 0
JudgementLine: 0
ScorePosition: 999
ComboPosition: 999
FontCombo: basefont
LightFramePerSecond: 6
ColumnWidth: 22,22,22,22,24,22,22,22,22
//Colours
Colour1: 0,0,0,255
Colour2: 0,0,0,255
Colour3: 0,0,0,255
Colour4: 0,0,0,255
Colour5: 0,0,0,255
Colour6: 0,0,0,255
Colour7: 0,0,0,255
Colour8: 0,0,0,255
Colour9: 0,0,0,255
ColourLight1: 112,153,92,255
ColourLight2: 61,102,41,255
ColourLight3: 112,153,92,255
ColourLight4: 61,102,41,255
ColourLight5: 112,153,92,255
ColourLight6: 61,102,41,255
ColourLight7: 112,153,92,255
ColourLight8: 61,102,41,255
ColourLight9: 112,153,92,255
ColourHold: 255,255,255,255
ColourBreak: 120,0,0,0
//images
ColumnLineWidth: 0,0,0,0,0,0,0,0,0,0
BarlineHeight: 1
This issue has been addressed by the following change by peppy:
Fix ProgressBarCircular not displaying correctly with OpenGL.
It will be applied to builds newer than b20141212cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Fix ProgressBarCircular not displaying correctly with OpenGL.
It will be applied to builds newer than b20141212cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
This issue has been addressed by the following change by smoogipooo:
Check for out of bounds errors while loading Mania skins.
It will be applied to builds newer than b20141212.1cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Check for out of bounds errors while loading Mania skins.
It will be applied to builds newer than b20141212.1cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
It looks like your Mania skins had a few extra columns in the ColumnWidth and ColumnLineWidth properties. Can you over your nK.ini configs in your skin so I can check if this is a migration error? Thanks!Garygoh884 wrote: 1e4r
I actually included the skin.ini within my skin folder. There was nothing wrong on the Stable release but never on the CuttingEdge version (after the Christmas update).peppy wrote: 73101g
You say this but you don't include your skin.ini?
Here are the nK.ini configs that I use for every keymode in Mania that each sums up to a fixed total of 200 units in ColumnWidth values. Because the maximum value for a ColumnWidth is 100, I used "null keylanes" to void out some lanes for 1K, 2K, and 3K modes, which each of its ColumnWidth values similar to that of 4K.ini's.smoogipooo wrote: 4a5y4s
It looks like your Mania skins had a few extra columns in the ColumnWidth and ColumnLineWidth properties. Can you over your nK.ini configs in your skin so I can check if this is a migration error? Thanks!Garygoh884 wrote: 1e4r
...
I actually included the skin.ini within my skin folder. There was nothing wrong on the Stable release but never on the CuttingEdge version (after the Christmas update).
Below are my nK.ini's you've requested for reference:
1K.ini
//Mania skin config
ColumnLineWidth: 0.7
ColumnStart: 40
BarlineWidth: 1.0
HitPosition: 413
SpecialStyle: 1
SpecialPositionLeft: 1
UpsideDown: 0
JudgementLine: 0
ScorePosition: 999
ComboPosition: 999
FontCombo: basefont
LightFramePerSecond: 6
ColumnWidth: 50,50,50,50
ColumnLine: 0,0,0,0,0
//Colours
Colour1: 0,0,0,255
Colour2: 0,0,0,255
Colour3: 0,0,0,255
Colour4: 0,0,0,255
ColourLight1: 112,153,92,140
ColourLight2: 0,0,0,0
ColourLight3: 0,0,0,0
ColourLight4: 0,0,0,0
ColourBreak: 120,0,0,0
KeyImage2: mania-keyN
KeyImage2D: mania-keyN
KeyImage3: mania-keyN
KeyImage3D: mania-keyN
KeyImage4: mania-keyN
KeyImage4D: mania-keyN
2K.ini
//Mania skin config
ColumnLineWidth: 0.7
ColumnStart: 40
BarlineWidth: 1.0
HitPosition: 413
SpecialStyle: 1
SpecialPositionLeft: 1
UpsideDown: 0
JudgementLine: 0
ScorePosition: 999
ComboPosition: 999
FontCombo: basefont
LightFramePerSecond: 6
ColumnWidth: 50,50,50,50
ColumnLine: 0,0,0,0,0
//Colours
Colour1: 0,0,0,255
Colour2: 0,0,0,255
Colour3: 0,0,0,255
Colour4: 0,0,0,255
ColourLight1: 112,153,92,140
ColourLight2: 112,153,92,140
ColourLight3: 0,0,0,0
ColourLight4: 0,0,0,0
ColourBreak: 120,0,0,0
KeyImage3: mania-keyN
KeyImage3D: mania-keyN
KeyImage4: mania-keyN
KeyImage4D: mania-keyN
3K.ini
//Mania skin config
ColumnLineWidth: 0.7
ColumnStart: 40
BarlineWidth: 1.0
HitPosition: 413
SpecialStyle: 1
SpecialPositionLeft: 1
UpsideDown: 0
JudgementLine: 0
ScorePosition: 999
ComboPosition: 999
FontCombo: basefont
LightFramePerSecond: 6
ColumnWidth: 50,50,50,50
ColumnLine: 0,0,0,0,0
//Colours
Colour1: 0,0,0,255
Colour2: 0,0,0,255
Colour3: 0,0,0,255
Colour4: 0,0,0,255
ColourLight1: 112,153,92,140
ColourLight2: 61,102,41,140
ColourLight3: 112,153,92,140
ColourLight4: 0,0,0,0
ColourBreak: 120,0,0,0
KeyImage4: mania-keyN
KeyImage4D: mania-keyN
4K.ini
//Mania skin config
ColumnLineWidth: 0.7
ColumnStart: 40
BarlineWidth: 1.0
HitPosition: 413
SpecialStyle: 1
SpecialPositionLeft: 1
UpsideDown: 0
JudgementLine: 0
ScorePosition: 999
ComboPosition: 999
FontCombo: basefont
LightFramePerSecond: 6
ColumnWidth: 50,50,50,50
ColumnLine: 0,0,0,0,0
//Colours
Colour1: 0,0,0,255
Colour2: 0,0,0,255
Colour3: 0,0,0,255
Colour4: 0,0,0,255
ColourLight1: 112,153,92,140
ColourLight2: 61,102,41,140
ColourLight3: 61,102,41,140
ColourLight4: 112,153,92,140
ColourBreak: 120,0,0,0
...5K to 8K works well, skipping to 9K...
9K.ini
//Mania skin config
ColumnLineWidth: 0.7
ColumnStart: 40
BarlineWidth: 1.0
HitPosition: 413
SpecialStyle: 0
SpecialPositionLeft: 0
UpsideDown: 0
JudgementLine: 0
ScorePosition: 999
ComboPosition: 999
FontCombo: basefont
LightFramePerSecond: 6
ColumnWidth: 22,22,22,22,24,22,22,22,22
ColumnLine: 0,0,0,0,0,0,0,0,0,0
//Colours
Colour1: 0,0,0,255
Colour2: 0,0,0,255
Colour3: 0,0,0,255
Colour4: 0,0,0,255
Colour5: 0,0,0,255
Colour6: 0,0,0,255
Colour7: 0,0,0,255
Colour8: 0,0,0,255
Colour9: 0,0,0,255
ColourLight1: 112,153,92,255
ColourLight2: 61,102,41,255
ColourLight3: 112,153,92,255
ColourLight4: 61,102,41,255
ColourLight5: 112,153,92,255
ColourLight6: 61,102,41,255
ColourLight7: 112,153,92,255
ColourLight8: 61,102,41,255
ColourLight9: 112,153,92,255
ColourHold: 255,255,255,255
ColourBreak: 120,0,0,0
//images
10K.ini
//Mania skin config
ColumnLineWidth: 0.7
ColumnStart: 40
BarlineWidth: 1.0
HitPosition: 413
SpecialStyle: 1
SpecialPositionLeft: 1
UpsideDown: 0
JudgementLine: 0
ScorePosition: 999
ComboPosition: 999
FontCombo: basefont
LightFramePerSecond: 6
ColumnWidth: 24,20,19,20,19,20,19,20,19,20
ColumnLine: 0,0,0,0,0,0,0,0,0,0,0
//Colours
Colour1: 0,0,0,255
Colour2: 0,0,0,255
Colour3: 0,0,0,255
Colour4: 0,0,0,255
Colour5: 0,0,0,255
Colour6: 0,0,0,255
Colour7: 0,0,0,255
Colour8: 0,0,0,255
Colour9: 0,0,0,255
Colour10: 0,0,0,255
ColourLight1: 156,156,156,255
ColourLight2: 112,153,92,255
ColourLight3: 61,102,41,255
ColourLight4: 112,153,92,255
ColourLight5: 61,102,41,255
ColourLight6: 112,153,92,255
ColourLight7: 61,102,41,255
ColourLight8: 112,153,92,255
ColourLight9: 61,102,41,255
ColourLight10: 112,153,92,255
ColourHold: 255,255,255,255
ColourBreak: 120,0,0,0
//images
KeyImage0: mania-keyX
KeyImage0D: mania-keyXD
KeyImage5: mania-keyS
KeyImage5D: mania-keySD
NoteImage0: mania-noteX
NoteImage0L: mania-noteXL
NoteImage0H: mania-noteXH
NoteImage5: mania-noteS
NoteImage5L: mania-noteSL
NoteImage5H: mania-noteSH
In addition to this, the height of each note are static and cannot be increased, which constantly does in the Stable release.
my sister just tried the taiko mode on this beatmap and the level didn't stop, however I've tried it again and it worked fine
YesJetzu wrote: 54433b
Is moving background when you move your cursor intended? I'd like to have my backgrounds sitll
Old bugMranth0ny62 wrote: z253p
my sister just tried the taiko mode on this beatmap and the level didn't stop, however I've tried it again and it worked fine
About the skin talk you guys had earlier, I'm having problems with mania key bindings not working in cutting edge (b20141212.2)
Doesn't matter if it's ed skin or default skin, if I define the bindings in ini file or ingame.
this is the skin.ini file that osu itself generates:
EDIT: discovered some aditional details.
When starting the game, the config is loaded correctly, but the osu!mania layout settings page is just not showing your actual configuration, and therefore if you open the configuration and doesn't change the fake config to your actual config (even though that's what you currently have) then the fake config will be written to disk.
Doesn't matter if it's ed skin or default skin, if I define the bindings in ini file or ingame.
this is the skin.ini file that osu itself generates:
skin.ini
Also I noticed something strange, 4 Keys bindings are placed after 5 Keys bindings and if I try to change it, the game just changes it back, not that it matters at all, just funny observation.[General]
Version: 2.4
[Mania]
Keys: 5
Key0: R
Key1: G
Key2: Space
Key3: J
Key4: I
[Mania]
Keys: 4
Key0: R
Key1: G
Key2: J
Key3: I
JudgementLine: 0
[Mania]
Keys: 6
Key0: E
Key1: R
Key2: G
Key3: J
Key4: I
Key5: O
[Mania]
Keys: 7
Key0: E
Key1: R
Key2: G
Key3: Space
Key4: J
Key5: I
Key6: O
[Mania]
Keys: 8
EDIT: discovered some aditional details.
When starting the game, the config is loaded correctly, but the osu!mania layout settings page is just not showing your actual configuration, and therefore if you open the configuration and doesn't change the fake config to your actual config (even though that's what you currently have) then the fake config will be written to disk.
This is actually an old issue not directly related to cutting edge changes. I've never been able to replicate it on a consistent basis so there isn't much to go on to point the devs in the right direction.Mranth0ny62 wrote: z253p
my sister just tried the taiko mode on this beatmap and the level didn't stop, however I've tried it again and it worked fine
Like I stated in my post (t/265937) the new sorting (with same songs), taiko below the normal diffs, is very odd, I think this needs to be changed.
drum drum mentioned this is intended behaviour, but I still find this very odd, read the thread for more info on this.
I'm sorry if drum drum is right, and we just need to get used to this new behaviour
drum drum mentioned this is intended behaviour, but I still find this very odd, read the thread for more info on this.
I'm sorry if drum drum is right, and we just need to get used to this new behaviour
Okay this bug is going on in a weird waybaraatje123 wrote: 5t724b
Kind of a weird bug
Play taiko mod /Edit Taiko mode (I don't know what triggers it exactly)
Then edit a Standard mode
The colors of the map are Red/Blue, and the sliders are the same colors as the Taiko skin (I think you need to have Taiko skin available and enable for playing Taiko)
When playing, it also shows the 'new' colors
When editing, it also shows the 'new' colors
When restarting, it still shows the 'new' colors
I don't really mind it, as red/blue are nice combo colors, but it would be nice if this can get fixed
1) Are they in the top 50? You should be able to watch them if they are.fizzn1 wrote: 7w44
b20141212.2
1.) I can't watch someone repaly.
2.) Where's a triangles in a main menu? Triangles are enabled
3.) i can't set-up my own main meun background.
2) Disabled for Christmas.
3) Currently disabled for Christmas.
1.) In top 50 menu.smoogipooo wrote: 4a5y4s
1) Are they in the top 50? You should be able to watch them if they are.fizzn1 wrote: 7w44
b20141212.2
1.) I can't watch someone repaly.
2.) Where's a triangles in a main menu? Triangles are enabled
3.) i can't set-up my own main meun background.
2) Disabled for Christmas.
3) Currently disabled for Christmas.
Similar bug here. It seems that whenever the Taiko skin is loaded (a play of a converted or original taiko map in my case), the skin.ini file from the current skin gets replaced by the skin.ini from the Taiko Skin.baraatje123 wrote: 5t724b
Okay this bug is going on in a weird waybaraatje123 wrote: 5t724b
Kind of a weird bug
Play taiko mod /Edit Taiko mode (I don't know what triggers it exactly)
Then edit a Standard mode
The colors of the map are Red/Blue, and the sliders are the same colors as the Taiko skin (I think you need to have Taiko skin available and enable for playing Taiko)
When playing, it also shows the 'new' colors
When editing, it also shows the 'new' colors
When restarting, it still shows the 'new' colors
I don't really mind it, as red/blue are nice combo colors, but it would be nice if this can get fixed
http://puu.sh/duqBz/15345f8285.webm
This issue has been addressed by the following change by smoogipooo:
Fix possible nullref exception when loading skins with invalid properties.
It will be applied to builds newer than b20141215.2cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Fix possible nullref exception when loading skins with invalid properties.
It will be applied to builds newer than b20141215.2cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
The scoreboard used to save the replays for the top 40 scores only. That was changed quite a while ago, however the replays past position 40 are still lost. The score you're trying to watch is very old, so it probably fell below the 40 line at some point, causing it to not save with any replay.fizzn1 wrote: 7w44
b20141212.2
1.) I can't watch someone repaly.
This issue has been addressed by the following change by smoogipooo:
Fix mania hidden and flashlight sprites.
It will be applied to builds newer than b20141215.3cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Fix mania hidden and flashlight sprites.
It will be applied to builds newer than b20141215.3cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Fallback to long note head if tail can't be loaded from skin.(Dec 15, 2014) It overrides the settings set in .ini file.
Screenshot:
Screenshot:
also something related to mania
the notes are just smaller lines and not correctly stretched.
EDIT: It may has been just this one time since after restarting osu they showed normally
Instead mania-stage-light is drawn over notes instead of behind and mania-stage-bottom is drawn behind the keys instead of above.
EDIT: It may has been just this one time since after restarting osu they showed normally
Instead mania-stage-light is drawn over notes instead of behind and mania-stage-bottom is drawn behind the keys instead of above.
This issue has been addressed by the following change by Damnae:
Fix incorrect background when multiple background updates happen in the same frame.
It will be applied to builds newer than b20141218cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Fix incorrect background when multiple background updates happen in the same frame.
It will be applied to builds newer than b20141218cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
This issue has been addressed by the following change by smoogipooo:
Make mania-stage-bottom draw above keys.
It will be applied to builds newer than b20141218.1cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Make mania-stage-bottom draw above keys.
It will be applied to builds newer than b20141218.1cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
This issue has been addressed by the following change by smoogipooo:
Fix incorrect fallback to slider note head image if tail can't be loaded.
It will be applied to builds newer than b20141218.1cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Fix incorrect fallback to slider note head image if tail can't be loaded.
It will be applied to builds newer than b20141218.1cuttingedge.
Please follow up in this thread on the status of this issue after you have tested it. If it has not yet been resolved, please provide any new details that may have arisen since before this change.
Actually in some cases in game-play, I saw the yellow bar show itself in game-play and it suppose to be hidden when in game-play and show during breaks. Usually I can replicate in CE when I am playing a song with NC or DT in CTB mode and the game ends up like a rushed messed.
Also is it just me or NC got more jittery in the CE Build?
Also is it just me or NC got more jittery in the CE Build?