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
-
Not sure if its just me but after upgrading to Magma V3.0, I was unable to get built songs to load into my setlist. Tried building songs several times and deleting my song cache and nothing. I went back to 2.2 and now songs load into my setlist. I even used a fresh folder with the new 3.0 install files in them and no go. Freakin weird.
It might not be you. I tried testing, but as I said, got zero beta testing feedback before. AddyMilldike already found two small bugs, if you can confirm what’s causing the problem, let me know and that’ll get fixed in next update.
I’ve made two songs so far without trouble loading it into the game. Is there anything you’re doing different this time? Perhaps using a feature in the new Magma that wasn’t present in the previous versions?
When I was using V3 I had the “Delete old RBA files before compiling” checked and after I built a CON the RBA files were still in the folder of the CON and not deleted. If I’m the only one having this problem then just ignore me. For now I went back to the older version and it works fine. If and when a newer update to Magma comes out I will try it again.
Not sure if it’s the same issue, but after using v3 I couldn’t see the song I had updated in my setlist. I could see it via xbox home. I deleted the song cache and it still couldn’t see it in the setlist until I actually moved the file from my thumbdrive to the hard drive, then deleted the cache and once the cache rebuilt, the song was there. Only tried this with one song over the past weekend. Thought it was my own stupidity. Still might be.
Here’s an idea. See if those songs “not showing up” have really long song IDs by any chance?There were several iterations, but I don’t think any were too long. I’ve had the name-too-long issue before so I’m usually watching for it. What is the maximum number of characters “allowed”?
Rough first day with Magma 3.0:
– Cannonball.rbproj shows pro g/b, but the resulting songs.dta didn’t have pro. Toggling it twice brought it back.
– Encryption also got turned off when loading my Friday rbproj files into 3.0.
– An upcoming song (13 char songs.dta entry) appears fine in xbox dashboard, but does not show up in game.
I’ll pm the details when I get electricity back.
– Encryption also got turned off when loading my Friday rbproj files into 3.0.
Mogg encryption is a Magma setting, not a song setting. You need to set your settings for Magma v3 again as it uses a different config file.
For the rest, I’ll need project files to test on my end.
I’m having an issue with MIDI Cleaner not receiving the filename I’m trying to clean. I now have to browse to the file to continue cleaning. Only a few extra clicks, but a real pita when debugging compile errors.
” src=”/wp-content/uploads/invision_emoticons/default_SA_frown.gif” /> v2.2 still works fine in this respect.
I’m working on an update. Will be going through all the reported bugs.
When I was using V3 I had the “Delete old RBA files before compiling” checked and after I built a CON the RBA files were still in the folder of the CON and not deleted.I highlighted the important parts of your statement. The option is to delete the existing RBA file before it creates a new one. After it creates the CON, it should leave the RBA there. That’s how it’s intended to be. In case you want to use Audition Mode or otherwise use the RBA file.
OK. Thanks.I’ll just use 22 to debug ’til then.
This was already implemented in the latest release of C3 CON Tools. If that’s what was keeping you from using updated Magma, you can use it now.
Here’s an idea. See if those songs “not showing up” have really long song IDs by any chance?There were several iterations, but I don’t think any were too long. I’ve had the name-too-long issue before so I’m usually watching for it. What is the maximum number of characters “allowed”?
If I remember correctly, 26 characters. Have you had any luck in getting songs with v3 showing up in game?
- You must be logged in to reply to this topic.