Magma: C3 Roks Edition v3.3.2 [07/28/15]
- This topic has 697 replies, 6 voices, and was last updated 1 year, 8 months ago by
.
-
Posts
-
Yeah, 2.2 still has the “New and Shiny” theme which is arguably much more usable. Might want to look into that.
Ah so more people are experiencing the issue where the songs dont show up in the setlist even if you delete the cache. I’m hesitant to upgrade to Magma V3.1 until this issue is solved.
That’s why I’m suggesting rebuilding the song cache. See if that works. If not pm me a link to the songs and I’ll take a look tonight.Ah so more people are experiencing the issue where the songs dont show up in the setlist even if you delete the cache. I’m hesitant to upgrade to Magma V3.1 until this issue is solved.So rebuilding the cache doesn’t work? Hm, I will try it anyway.
There is a severe lack of communication going on. Nobody has yet reported that a song was compiled in v3.1 that doesn’t show in game. If it was compiled with v3.0 and then with v3.1 and no cache rebuild is happening in between, it might just not be showing because the cache was messed up as a result of the v3.0 version.
Besides the bug fixed in v3.1 there is nothing else that should break songs showing up in game. I don’t have the time to test and mess with my Xbox. So unless and until a few people report their experiences with v3.1 (rebuilding their cache if they used v3.0) there’s nothing else I can do…
So if there is an interest in using the new features added in v3 it’s up to you, the users, to give me comprehensive feedback if you want me to continue to work on this tool. Otherwise I’ll assume there is no interest and I won’t waste my time.
So if there is an interest in using the new features added in v3 it’s up to you, the users, to give me comprehensive feedback if you want me to continue to work on this tool. Otherwise I’ll assume there is no interest and I won’t waste my time.I guess we are all grateful for your work you put into Magma C3, the C3 Con Tools, etc.
I will rebuild my cache in a few minutes. Germany has another time zone, so I went to bed after pasting the song.dta files and was basically in my bed or at work while I posted the other replies.
” src=”/wp-content/uploads/invision_emoticons/default_SA_cheeky.001.gif” /> I had no chance to rebuild my song cache since then.Since I am at home now, I have access to my Xbox. Await feedback in a couple of minutes.
That’s fine. I’m not in any hurry. Just posted that so there is no surprise if I don’t put any more effort into this tool until and unless I see an interest in it.
That’s fine. I’m not in any hurry. Just posted that so there is no surprise if I don’t put any more effort into this tool until and unless I see an interest in it.OK. First I forgot to replace my v2.2 compiled songs with the v3.1 ones and then I forgot what I actually wanted to do in Rock Band…
” src=”/wp-content/uploads/invision_emoticons/default_SA_biggrin.gif” /> Anyway, I rebuild my song cache and the v3.1 compiled songs are showing up! I have currently no access to a Windows computer, so I can’t try new compiled songs. But the 2 ones from yesterday are showing up.
I just compiled a song with Magma C3 Roks V3.1 and the song showed up in my setlist without having to delete the cache. Looks like the song not showing up in the setlist bug is fixed. The only feature I miss from Magma 2.2 is that it would delete the RBA file after a CON was build successfully. Other than that I’ll be staying on this new version for now.
I just compiled a song with Magma C3 Roks V3.1 and the song showed up in my setlist without having to delete the cache. Looks like the song not showing up in the setlist bug is fixed. The only feature I miss from Magma 2.2 is that it would delete the RBA file after a CON was build successfully. Other than that I’ll be staying on this new version for now.Does your 3.1 attach the version to the file name?
I just compiled a song with Magma C3 Roks V3.1 and the song showed up in my setlist without having to delete the cache. Looks like the song not showing up in the setlist bug is fixed. The only feature I miss from Magma 2.2 is that it would delete the RBA file after a CON was build successfully. Other than that I’ll be staying on this new version for now.Does your 3.1 attach the version to the file name?
Yes, that feature works for me.
I just compiled a song with Magma C3 Roks V3.1 and the song showed up in my setlist without having to delete the cache. Looks like the song not showing up in the setlist bug is fixed. The only feature I miss from Magma 2.2 is that it would delete the RBA file after a CON was build successfully. Other than that I’ll be staying on this new version for now.Does your 3.1 attach the version to the file name?
Yes, that feature works for me.
Hm, then it must be something on my end.
I just compiled a song with Magma C3 Roks V3.1 and the song showed up in my setlist without having to delete the cache. Looks like the song not showing up in the setlist bug is fixed. The only feature I miss from Magma 2.2 is that it would delete the RBA file after a CON was build successfully. Other than that I’ll be staying on this new version for now.Does your 3.1 attach the version to the file name?
Yes, that feature works for me.
Hm, then it must be something on my end.
Before installing Magma 3.1 on your system, I would completely unistall a previous version. Delete the old version completely instead of just overwriting 3.1 over 2.2 or 3.0. You probably already did this but just making sure.
I just compiled a song with Magma C3 Roks V3.1 and the song showed up in my setlist without having to delete the cache. Looks like the song not showing up in the setlist bug is fixed. The only feature I miss from Magma 2.2 is that it would delete the RBA file after a CON was build successfully. Other than that I’ll be staying on this new version for now.Does your 3.1 attach the version to the file name?
Yes, that feature works for me.
Hm, then it must be something on my end.
Before installing Magma 3.1 on your system, I would completely unistall a previous version. Delete the old version completely instead of just overwriting 3.1 over 2.2 or 3.0. You probably already did this but just making sure.
I’m stupid. Why do I think about downloading 2.2 and not re-downloading 3.1… Thanks for that, I will try it.
v3.2
NEW FEATURES
- Added option to replace song ID with a unique numeric value - enable in Options -> Use unique numeric song ID. More information on this will be posted in the forum thread
- Added explanations that will show for the more typical errors users experience during compilation and while using MIDI Tester
FIXES
- Removed context menu showing up when left-clicking on audio boxes as this broke ability to click and type into them - can still bring up context menus by right-clicking
- Fixed error thrown by compiler if author didn't change the genre/subgenre from default value
- Fixed bug where pro guitar or pro bass wouldn't save if you only enabled it but didn't click on a difficulty bubble
- Included blank backing audio required for MIDI Tester that was left out of last release
- Other minor fixes and improvements
HOW TO – MAKE YOUR CUSTOM BE CACHE WIPE PROOF!
So, PS3 users hamburgerjung and dahnlee figured out how to get customs to save scores from play session to session on the PS3, which doesn’t use song caches like the Xbox and Wii do. As a result of their discovery, I was able to translate that to Xbox and implement it on Magma: C3 Roks Edition. The end result is customs will no longer have alphanumeric song IDs, but instead will have unique numeric IDs (if you choose to use this system, which I highly suggest you do). This allows you to play a custom song, delete your song cache, and have the score stay. If you’re playing customs on Wii, this means you can now play customs online without any work on your end.
So, how is it done? To be clear, this will ONLY cache wipe proof customs you compile with this or a newer version of Magma: C3 Roks Edition. This will not fix existing customs, that will come next. Here are the steps you need to make this happen…
Start by using Magma: C3 Roks Edition v3.2 or newer.
Click on Options, and then click on “Use unique numeric song ID”
If this is the first time you’re enabling it, you’ll get a prompt that give you some basic information. Read it.
From any point here on the C3 Forums, click on the “PROFILE” button at the top. Right under the “Front Page” header, you’ll find your ID where it says “Your author ID: XXXXX”.
Enter this ID (the digits only) on the prompt or by clicking on Option -> Use unique numeric song ID -> Change Author ID.
If this is the first time you’re doing this, leave the song counter as is. If you’ve already been working with this, and your computer blew up and you don’t want to conflict with your existing customs, you can change the song counter at this prompt or by clicking on Option -> Use unique numeric song ID -> Change song number
That’s all there is to it. Compile the custom as you normally would. Place it on your Xbox. Play. Delete cache. Find score still there!
I hope everyone jumps on board with this. Cache wiping fixes a LOT of problems, and until now the problem was “I don’t want to lose my scores.” Well, if you all work with me on this, we can eliminate that forever.
- You must be logged in to reply to this topic.