Magma: C3 Roks Edition v3.3.2 [07/28/15]
- This topic has 697 replies, 6 voices, and was last updated 1 year, 9 months ago by
.
-
Posts
-
I have been unable to get my current custom to have that look and feel that I need for it. I have changed the theme every time I compile it and nothing appears different each time as far as post processing effects. I get camera changes, guitar solo animations and fireworks but no post processing at all. We all know what to expect from the dark heavy rock theme, but I get nothing. Once I learned about the importance of genre for this, I started changing that too but to no avail. There are so many to choose from and figuring what the differences is going to take some time but I started with any that look like they’d compliment a dark, slow jam like Blues or Jazz and such, but no change that I can tell. My very first custom was dark heavy rock & it worked as expected. This time I had to export the theme before I was able to get any results. I also just realized that I haven’t seen ANY post processing effects in many of my more recent customs. I wouldn’t have noticed unless I was trying for something more than just random, general effects as I am now. I plan on going back through my customs to see where things might have changed but in the meantime I wanted to make Trojan aware of this (in case it’s not just me) and see if anyone else has noticed a lack of detail to their auto-generated venues.
That’s nothing that I have modified or will be modifying. The autogen of the venue only works if you don’t already have a venue in your MIDI file, and it is based on your selected theme and influenced by the practice sessions. It’s not something that Magma does, but MagmaCompiler, and it’s not something I have anything to do with. It’s also bad practice to rely on it to do the venues for you. You want a custom venue, do it manually
” src=”/wp-content/uploads/invision_emoticons/default_SA_wink.gif” />Unlikely request, but for Pro Keys, could you allow sharp/flat notes that are a semitone out of range to pass?Not something I’m currently blocking. If it doesn’t work now, it’s because MagmaCompiler blocks it. If some C3 songs have it, that means you should be able to do it as well.
Not something I’m currently blocking. If it doesn’t work now, it’s because MagmaCompiler blocks it. If some C3 songs have it, that means you should be able to do it as well.
Actually, no, C3 songs, like any other songs, have no notes outside of the ranges, because it’s not allowed. What it’s seen in the screenshot is a blatantly improper positioning of the range shifters, which need to happen roughly a measure before notes go out of range. Magma will not raise an exception for range shifts placed too late (mainly because it depends on tempo probably), only notes out of range.
I get that Magma Compiler has nothing to do with you or anything you mess with (well now I know). I only know about your Magma program but not the compiler that your program is wrapped around. Using your Magma when I choose an automated theme I thought it is supposed to auto-generate (with post processing effects included) as long as your venue track is empty? My template and all my customs (save 1 that I manually created) have VENUE track and [lighting ()] only. Is this incorrect and the reason for my issue? I just went through all my previous work and all but the first 3 have not a single .pp effect in game. 2 of those were auto-generated so I know it worked a while ago but not since for some reason.
For autogen to work, whatever you’re trying to autogen can’t already be there. If you have a VENUE track, it won’t autogen one. Similarly, if you’ve put ANY anim markers for drums, it won’t work either.
Alright. I was under the impression you can have a Venue track as long as you don’t add to it. Didn’t realize I needed to delete the track entirely. Now I get to recompile 13 customs.
For autogen to work, whatever you’re trying to autogen can’t already be there. If you have a VENUE track, it won’t autogen one. Similarly, if you’ve put ANY anim markers for drums, it won’t work either.I believe autogen will still work if the VENUE track has nothing but the track name in it. I think the only reason why autogen didn’t work for djmike was because he still had the [lighting ()] event in it.
For autogen to work, whatever you’re trying to autogen can’t already be there. If you have a VENUE track, it won’t autogen one. Similarly, if you’ve put ANY anim markers for drums, it won’t work either.I believe autogen will still work if the VENUE track has nothing but the track name in it. I think the only reason why autogen didn’t work for djmike was because he still had the [lighting ()] event in it.
That would be correct. It’s possible to manually create a venue track full of lighting events, but no camera events. Magma will only generate the camera events in this case. However, if there’s even one event of either a camera or lighting event, then Magma will not generate anything for the type of events that are present in the track when compiling.
That makes total sense, thank you guys. It always said skipping camera and lighting cues, but once I deleted the venue track with the [lighting ()] in it, it read skipping Lighting + post processing cues. Funny thing is, that 1 lighting event was in the C3 custom template. I would not have known what that event even was to add it myself so I don’t know why it’s there… updated template. Still have to recompile and update my posts but at least this won’t happen again.
Peace
Funny thing is, that 1 lighting event was in the C3 custom template.That’s a significant issue, maybe Nyx can look into that and fix it.
Unlikely request, but for Pro Keys, could you allow sharp/flat notes that are a semitone out of range to pass?Not something I’m currently blocking. If it doesn’t work now, it’s because MagmaCompiler blocks it. If some C3 songs have it, that means you should be able to do it as well.
I mainly asked because I didn’t know if it’s something you would be able to unblock or just choose not to. Currently the compiler doesn’t allow it and it’s technically not allowed but you can still see the notes in the lane
Playing on a Real Keyboard via Midi Pro Adapter it’s annoying for me to play wrapped notes so i was hoping to bypass that or something. Of course anything I hope to get on C3 will still follow the rules.
If it’s blocked by MagmaCompiler it can only be edited by hacking at the executable in IDA since we don’t have the source code and it wasn’t created in C# like Magma. My friend who helped with the assembly hacking in the early days of Magma: C3 is no longer around to help and I can’t accomplish it on my own. Not to mention every one thing we did broke multiple others that I had to then manually patch in to Magma…so in other words, it’s not happening if it’s up to me to make it happen.
- You must be logged in to reply to this topic.