[djmike534]

Hey guys, play-testing my current project has introduced me to a problem I have only heard about happening to xbox users that don’t have a proper TU4 but I am on a ps3. I do not believe this is a console issue tho.

When my custom starts, the camera is over the crowd aimed at the stage and it never changes. Guitar & bass shuffle around until they bug out and walk out of view while the singer plays with the mic like in idle tho his lips are still moving. All instruments have play markers in acceptable locations. Tried autogen on venue as usual and even exported one and replaced my blank venue with that on my last attempt. Nothing looks missing, wrong or out of place anywhere. I tried creating a fresh magma template for the song. I am at a loss on this one. Anyone familiar with this issue?

[djmike534]

Update:

Still not fixed, tho I now tried starting with a new reaper template and ported over just the notes from the original. Out of ideas now. The custom is finished otherwise so I’ll be releasing tomorrow regardless as gameplay is not affected, just a strange visual glitch.

There is one more issue that MAY be part of it or a totally different problem and that is an incorrect song length if you open the “additional info” of the song in the music library. My custom is 7:22 but in game it reads as 3:25.

If anyone has a thought on either of these I’d really be grateful.

Thanks

[StackOverflow0x]

Latest Magma? Usually it’s a title update issue. I see this on Wii a lot because only converted RBN1 venues work properly. The version might affect that combination too, but you shouldn’t have to change it.

[djmike534]

Thanks for responding

Although I am not on the latest Magma (326) I have had no problems with it thus far. I’ve made no changes recently to reaper, magma or C3tools and my last custom was fine. I will update magma today just to be thorough. I always use the correct template and I’m positive of that on the recent copy/paste I mentioned in my last post so I don’t know why the venue would decide to bug out now. My first thought was song length but after talking to someone who charted a 22 minute song I know it’s not that.

 

While writing this I am looking through all my past projects and noticed a size discrepancy on this one. The rpp file is at least double the size of all but one at 1,058k but it is my longest song so far. I had at first thought that this is from the flac audio I started using for best sound quality but audio isn’t exported in the midi and that is still very small. Is there a size limit perhaps on anything?

Oh and what ‘version’ are you referring to?

[TrojanNemo]

Is there a size limit perhaps on anything?

 

MIDI fed to Magma can’t be over 1MB. It should tell you if that’s the case.

[djmike534]

Thanks but yeah the mid is just 190k.

Could it be possible that the venue and incorrect song length issues are related in any way?

 

If anyone is interested in looking or just bored at work I am posting the rpp.

 

*link removed*

 

Thanks

[Kemiroch]

I have a couple of songs that do this too, although they are ones I have gotten from other users and not ones I’ve built myself.

 

I might have a look at yours and see if I can find any commonalities.

[djmike534]

Well It is fixed. Holy crap it was a pain in the ass and I STILL don’t know what it was exactly. I have to say that if the PS3 does not have a cache (does it?) then it must be magma. It would not work correctly in game until I gave it a completely different filename. I had it working once after I started with a fresh magma file I named ‘fixtest’ and as soon as I renamed it back to ‘rockme’ in magma it stopped working again. Even after deleting everything but the mid, dryvox, backing.wav and jpg it would not work. Same mid, dryvox, backing & jpg and starting a new instance of magma with the name ‘greatwhiterockme’ and cameras finally work as they should. Perhaps it holds some data even after deleting all the files from the project folder? Thanks to those that looked over the reaper file anyways. Updating customs post in a few.

[Farottone]

You just needed to change the song ID, it’s not Magma’s fault. ” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif”>

[djmike534]

But when I deleted all magma files and started from scratch, it would have produced a new song ID, wouldn’t it? See that’s why I was thinking that magma stills has data somewhere. Also I always replaced the song data in the main dta before testing every time so all data would be updated, including ID. All man, I almost hope it’s something less simple than song ID after the time took to fix it.

[Farottone]

But when I deleted all magma files and started from scratch, it would have produced a new song ID, wouldn’t it?

 

It depends. If you’re using the “use filename as song ID” system, nope.

[TrojanNemo]

See that’s why I was thinking that magma stills has data somewhere.

 

Magma: C3 Roks Edition doesn’t keep any project files anywhere except where you put them. The only things stored by Magma are configuration files for your preferred settings and to keep the song ID counter going.

[Author]

Posts