|
Subjunctive posted:That's going to make for some fun debugging, having totally different runtimes underlying the development and deployment environments. I saw on twitter someone was asking about debugging and they said: MonoDevelop and UnityVs should continue to work. They also want the CPP debugger to work (not sure what they mean here exactly. If that means you can just use a regular CPP debugger instead of UnityVs or if they mean being able to debug the CPP generated code).
|
#
?
May 20, 2014 22:59
|
|
|
|
| # ? Jun 3, 2024 11:37 |
|
|
Shalinor posted:
I picked one of these up: It was a pain in the rear end to get its clunky 6 year old editor to detect the device on Windows 7 but once I did, things seem to work fine. Some parts of the manuals are practically incomprehensible. You can configure it just about any way you want, as far as MIDI output. If you want to make all the buttons keyboard(music) keys, you can do that. You can configure them individually to be momentary or toggle too. This works pretty good for Unity input but I've only messed with it for 5 minutes so far. https://github.com/keijiro/unity-midi-input Obsurveyor fucked around with this message at 23:35 on May 20, 2014 |
|
#
?
May 20, 2014 23:33
|
|
|
Obsurveyor posted:If you want to make all the buttons keyboard(music) keys, you can do that. Although if that's all someone wants, they should get a NanoKey rather than a NanoKontrol.
|
|
#
?
May 20, 2014 23:55
|
|
|
Nition posted:Now now, there's absolutely no reason to suspect that Unity's entirely in-house, closed-source, massively cross-platform custom native compiler implementation will have any bugs or differences with the existing implementation. The good news is that IL is well-specified semantically, and there are decent test suites for it. As long as they don't try to get clever with just-so shortcuts and actually run the test suites and so forth.  xgalaxy posted:I saw on twitter someone was asking about debugging and they said: Debugging C++ code that has been through C# compilation, IL2CPP, and a C++ optimization pass is going to be pure, unadulterated  I'm sure MonoDevelop will keep working, it'll just be a different runtime than deployment, especially in relative performance of different operations. I wonder how profiling will work. Subjunctive fucked around with this message at 02:04 on May 21, 2014 |
|
#
?
May 21, 2014 02:01
|
|
|
ClownSyndrome posted:My LD game came in 3rd place in the Jam humour list! I love it! The cursing was the best part because I was doing it at the same time 
|
|
#
?
May 21, 2014 02:44
|
|
|
the chaos engine posted:
my god this is amazing
|
|
#
?
May 21, 2014 09:14
|
|
|
Coldrice posted:my god this is amazing Thanks Somehow ending up my most complicated game, feature-wise. Level select, inventory, weapon switching, all this poo poo is new to me.
|
|
#
?
May 21, 2014 11:44
|
|
|
This 32x32-challenge reminds me a lot of Nitrome's Icon games. By clicking of the icon of those games, you can directly play them in the game select screen.
|
|
#
?
May 21, 2014 12:17
|
|
|
Game maker has decided it doesn't like keyboard inputs any more.  Edit and then I immediately fixed it. It's amazing what a good night's sleep can do for your brain. Shoehead fucked around with this message at 12:51 on May 21, 2014 |
|
#
?
May 21, 2014 12:44
|
|
|
How much do people expect increasing numbers in a JRPG type game? I want to keep number inflation low in my game, and show progression through changes in available moves, but I also understand that people like to see numbers go up. A second question - what are your balancing methodologies in RPG type games? For my basic benchmark enemy I've decided on the numbers based on how many would be needed to take the main character down, and how many I want her to be able to take down in a round.
|
|
#
?
May 21, 2014 13:28
|
|
|
Angrymog posted:How much do people expect increasing numbers in a JRPG type game? It really depends – Mario-RPGs always have very small and manageable numbers, whereas Final Fantasy is well known for reaching 4-digit numbers fast. Development is going okay. I converted my code to C# and started implementing a state machine, although I'm slowly reaching the point where it's starting to get overwhelming. Maybe I should focus on something else, like HUD, menu design, concept art or even 3D modeling, which I have almost no experience with. That being said, here's a little gif of a mockup for one of the weapons in the game. 
|
|
#
?
May 21, 2014 14:07
|
|
|
Hopefully Unity will allow developers to skip IL2CPP conversion for projects that don't really need to be optimized in favor of better parity with development builds (and easier debugging).
|
|
#
?
May 21, 2014 15:11
|
|
|
Bert of the Forest posted:Gamemaker does have layers via their object depth system. To achieve what you're describing, you can go into the step event of the players and create a script that looks something like this: Hey it worked, thanks! 
|
|
#
?
May 21, 2014 15:11
|
|
|
I preffered the bigger shark - the little guy is cute, but its pretty easy to lose him against the background. e: Collision masks The problem with a foot only mask is that there's then no way to detect when you've been hit. (detecting when you've hit something is easy - iirc you can swop your masks in code, so you could swop to a full body mask when you hit the attack button, but doing the same when you've been hit is different, unless you use a collision with someone elses's foot mask as a trigger for loading the full mask in or something.) Angrymog fucked around with this message at 15:32 on May 21, 2014 |
|
#
?
May 21, 2014 15:19
|
|
|
Angrymog posted:I preffered the bigger shark - the little guy is cute, but its pretty easy to lose him against the background. My background palette is totally going to have to change, along with the scale. I think the worst part of the bg at the moment is that dead tv. I want to make the background much darker to make it look more like night and to make my sprites pop a bit more. Gonna test out different hitboxes later tonight with a friend maybe, the feet might be too precise. Edit: Isn't there a function for sensing if there is a hitbox nearby? Maybe I could keep the feet collision but set it up so that if you are within the right distance on both axis' you can hit each other. That does mean you might be able to punch each other while facing the wrong way though.. Shoehead fucked around with this message at 15:48 on May 21, 2014 |
|
#
?
May 21, 2014 15:42
|
|
|
Or maybe keep it simple - just assume that two people who's foot masks are touching and are facing the right way can hit each other.
|
|
#
?
May 21, 2014 16:42
|
|
|
Angrymog posted:Or maybe keep it simple - just assume that two people who's foot masks are touching and are facing the right way can hit each other. Yeah, atm they are 1 pixel tall, which might be a tad bit too small..
|
|
#
?
May 21, 2014 17:21
|
|
|
Think when I did something like that I give the collision mask a similar size and position to a circular shadow under the players feet Also handy when you want a character to jumps (y position of mask stays the same, but sprite is offset based on who far off the ground they should be)
|
|
#
?
May 21, 2014 17:25
|
|
|
I think I'm going to change how I handle depth too. The way I have it atm is your depth goes up or down as you move but I think I'll have it so that when you cross a point it'll change. It seems more controllable that way. I uh.. might be overthinking all of this...
|
|
#
?
May 21, 2014 18:14
|
|
|
Added some cool features to my game yesterday, boomerangs, ladders, and a toggle-able debug mode to help me develop that draws simple colored rectangles over all the level metadata so I'm not working blind on collisions and stuff. Every little bit helps, just gotta keep at it! Its daunting to look at all the things I want done, but if you chip away at it day by day its not so bad. My artist friend just left town without telling me so I'm giving up on ever getting anything out of him, just gonna make a game with ripped castlevania sprites, gently caress the bullshit. 
|
|
#
?
May 21, 2014 18:15
|
|
|
Shoehead posted:I think I'm going to change how I handle depth too. The way I have it atm is your depth goes up or down as you move but I think I'll have it so that when you cross a point it'll change. It seems more controllable that way. I uh.. might be overthinking all of this... I think the way you have depth going atm is the most elegant way to handle it. If you want larger steps multipy y by something before you invert it.
|
|
#
?
May 21, 2014 18:34
|
|
|
Zaphod42 posted:My artist friend just left town without telling me so I'm giving up on ever getting anything out of him, just gonna make a game with ripped castlevania sprites, gently caress the bullshit. Welcome to game development. Have you tried doodling the art yourself? It's better than nothing!
|
|
#
?
May 21, 2014 18:50
|
|
|
Well at the moment it's leading to stuff like this So I need to tweak something at least.
|
|
#
?
May 21, 2014 18:50
|
|
|
Shoehead posted:Well at the moment it's leading to stuff like this
|
|
#
?
May 21, 2014 19:05
|
|
|
Yeah just set every sprite's origin to be right at their feet.
|
|
#
?
May 21, 2014 19:07
|
|
|
Angrymog posted:Where is your sprite's origin point, and where are you doing the depth change - in the draw event? Dead centre. And every time he moves up and down unless he's stopped. Manslaughter posted:Yeah just set every sprite's origin to be right at their feet.
|
|
#
?
May 21, 2014 19:14
|
|
|
Nition posted:Are you using named or default parameters in your methods? MonoBehaviours in namespaces combined with named/default parameters breaks Unity. I was initially. But when trying to fix it I read about that bug and removed them but kept having the problem. But I can't seem to recreate the issue now so maybe I missed a default parameter in my initial attempts to fix it before removing the namespace. Or some other change elsewhere fixed it somehow. Specifically I was using a ScriptableObject and when inside the namespace Unity would just forget which script was assigned to the ScriptableObject/asset when closing/reopening the project. It worked fine right after creating the object but after reopening Unity and selecting the object it would just display  Even though there weren't any compile errors. Telling it which script to use would fix it, it wouldn't lose any data, I'd just have to reassign the script every time I ran Unity and then reassign the object to any prefabs that had references to it.
|
|
#
?
May 21, 2014 19:17
|
|
|
Shoehead posted:Oh son of a bitch! code:
|
|
#
?
May 21, 2014 19:52
|
|
|
Spek posted:I was initially. But when trying to fix it I read about that bug and removed them but kept having the problem. But I can't seem to recreate the issue now so maybe I missed a default parameter in my initial attempts to fix it before removing the namespace. Or some other change elsewhere fixed it somehow. That is how the named/default parameter bug shows up, but there could be something else that causes it as well. I had a similar issue where I thought I'd removed them all but one MonoBehaviour script was still doing that.
|
|
#
?
May 21, 2014 21:11
|
|
|
Shoehead posted:Well at the moment it's leading to stuff like this Not so rough Hammerhead-san~
|
|
#
?
May 21, 2014 22:19
|
|
|
Yodzilla posted:Not so rough Hammerhead-san~ 
|
|
#
?
May 21, 2014 22:28
|
|
|
Ahaha. Ok setting the centre to their feet didn't help so instead I've set up a bunch of horizontal lines that would change your depth depending on your vertical motion, which broke my collision  It mostly works except moving over the line too quickly would double your depth and ruin everything.Edit: Wait fuckin' hell why don't I just check if my player's Y value is higher or lower than the enemy's, have him clip over or under the enemy and then reset when I move away? Shoehead fucked around with this message at 23:27 on May 21, 2014 |
|
#
?
May 21, 2014 23:11
|
|
|
Couldn't you make a thing that checks an area around their feet and ensures those boxes can't pass through one another (or attempts to push them if they overlap like they what happens in post-NES beat 'em ups)? It'll prevent weird clipping issues, at least.
|
|
#
?
May 21, 2014 23:38
|
|
|
Guys I WAS RIGHT  It only does it in relation to one sprite atm, which will cause problems later but it's close enough for now!
|
|
#
?
May 21, 2014 23:44
|
|
|
This is more art/ui theory or whatever, but what do you guys consider to be a really good textbox/dialog box? What qualities does one have, and what games do you consider to have the best ones? I like the blue gradient with white text that the Final Fantasy series goes with (but this might be nostalgia). Conversely, I think the Dragon Age and TES:Oblivion have dogshit textboxes.
|
|
#
?
May 21, 2014 23:49
|
|
|
Ulta posted:This is more art/ui theory or whatever, but what do you guys consider to be a really good textbox/dialog box? What qualities does one have, and what games do you consider to have the best ones? I like the blue gradient with white text that the Final Fantasy series goes with (but this might be nostalgia). Conversely, I think the Dragon Age and TES:Oblivion have dogshit textboxes. The problem with that textbox is that every default RPG Maker game uses it. As for good textboxes...     Maybe I just like colorful text boxes? 
|
|
#
?
May 22, 2014 01:37
|
|
|
If you can easily read it it's probably at least a decent text box. Persona 4's are fantastic however.
|
|
#
?
May 22, 2014 01:39
|
|
|
I personally like them bare on the inside with some high contrast text and then a fancy border.
|
|
#
?
May 22, 2014 01:45
|
|
|
Shoehead posted:Guys I WAS RIGHT Seriously depth = -y is the only way I've seen it done, you're gonna run into big problems unless you figure it out.
|
|
#
?
May 22, 2014 02:03
|
|
|
|
| # ? Jun 3, 2024 11:37 |
|
|
Shoehead posted:Edit: Wait fuckin' hell why don't I just check if my player's Y value is higher or lower than the enemy's, have him clip over or under the enemy and then reset when I move away? Don't do this. There are lots of potential issues with that solution. What if the character's origins are at different heights? What if the origin is in the centre, but the characters are different heights? You'll also have to be constantly checking against every enemy. When you have multiple enemies on screen, they'll all have to be checking against each other. If you forget one, it'll break. It'll be messy. Just set every character's depth based on the y position of their base (their feet). You can set it every game tick, or you can set it whenever they move up or down. It's simple, it'll work.
|
|
#
?
May 22, 2014 02:53
|
|