Jump to content

flux

New Members
  • Content Count

    48
  • Joined

  • Last visited

Community Reputation

33 Excellent

About flux

  • Rank
    Space Invader
  1. I got stuck on this issue a while back and decided to get back into it and still wasn't able to come up with a solution so I'm going to try reaching out. I have a 1 bit 16x16 single frame sprite that refuses to show up. I tried making a 64x64 1 bit sprite using the same program and method and it seems to load ok (the palette seems off but it's there at least). But the 16x16 version inexplicably refuses to appear. The changes I make in rapinit.s between the two are on these lines: dc.l 16 ; sprite_width ; width of sprite (in pixels) dc.l 16 ; sprite_height ; height of sprite (in pixels) dc.l 1 ; (BIT DEPTH) ; bitmap depth (1/2/4/8/16/24) dc.l 16*16/8 ; sprite_framesz ; size per frame in bytes of sprite data dc.l 16/8 ; sprite_bytewid ; width in bytes of one line of sprite data dc.l 16/8 ; sprite_gwidth ; GFX width (of data) dc.l 64 ; sprite_width ; width of sprite (in pixels) dc.l 64 ; sprite_height ; height of sprite (in pixels) dc.l 1 ; (BIT DEPTH) ; bitmap depth (1/2/4/8/64/24) dc.l 64*64/8 ; sprite_framesz ; size per frame in bytes of sprite data dc.l 64/8 ; sprite_bytewid ; width in bytes of one line of sprite data dc.l 64/8 ; sprite_gwidth ; GFX width (of data) Besides specifying a different filename in assets.txt, that's really the only thing that changes and I'm not sure why it would show up in one instance and not the other. I did clear out the build files and everything when switching between the two different files. I'm still not 100% clear on the whole dividing by 8 or 2 thing but I feel like I have it correct there. Once, when playing around with those numbers I did get my sprite to appear when I changed sprite_bytewid to 16/2. It was as tall as it should be but was maybe 4 or 5 times as wide, like a big rectangle instead of a square with the graphic all distorted and messed around (not simply stretched). Both 16/16 and 16/4 left me with my sprite still not appearing, and 16/1 gave me an even wider rectangle, perhaps twice as wide. So it may well be the case that I'm doing something wrong in that rapinit.s file but as I have it there in the code paste, it simply doesn't appear at all. (It might also be worth noting I don't have transparency turned on for that sprite or anything like that.)
  2. I remember a sales clerk urging me not to get Wolfenstein 3D, which I was getting mainly because I remembered having a ton of fun playing it on my friend's PC. He kept trynna push AvP on me and I refused. I did ultimately end up getting it maybe a few months later when I started to hear more good things about it.
  3. I played around with one of mine for a bit and the only issue I noticed is that the XYZ buttons seem to require you to press them a little hard. If you have a light touch, you can press them so the button goes to a seemingly pushed down state, but it doesn't register. You gotta be a bit mindful and make sure to give it just a little something extra. The Y button in particular is worse about that. I've noticed it with Z a bit too though. I haven't tried my other new controllers and I never used an original Pro so I can't say how it compares or if that issue with this one is a fluke. I much prefer this to the original 3 button pad though. Everything feels nice. The buttons feel nicer. Never really cared for the squishy feel of the ABC buttons on the original. And the L and R clicks on these are so satisfying. Really grateful Starwander did this.
  4. I guess we're queue buddies! I saw the email come in but I was at a local Fortnite competition my son was participating in, and I didn't want to mess around with it there and preferred to wait until I got home on my computer. Just glad I didn't wait too long!
  5. That was it exactly. I was looking for something like that curframe but wasn't able to find anything. Is there a complete list of those things? I was pretty much going by what was in some default rapinit.s template and if it's not there then I don't know about it. But yeah, I did as you suggested and it looks much better. Thanks again! As a side note, while I was stuck there, I took the time to add some code to capture button sequences for use in things like special moves or codes or something like that. They don't do anything yet, but I can see them and it seems to work pretty well.
  6. I was able to get started from the information in that thread but I'm still having some trouble working through this. I might be mistaken about what is happening, but this is what it looks like to me. Currently I have 6 frames spread over two 3-frame animations. When I press the button to shift to the punch animation, it doesn't seem to start from the beginning. For instance, if I pressed the button while on the second frame of the normal "idle" animation, then the punch animation will start on its respective third frame. I'm not sure if that's exactly, but it never really seems to go through the entire punch animation, and it definitely produces a separate and distinctly incomplete animation based on what frame of my idle animation I start on. My sprite is 80 pixels wide. Each frame is 128 pixels high (so with all 6, the spritesheet is 80x768). I'm adding 15360 when I hit the button, which if I understood the post you linked properly, it the number I'm to add in order to have it play the second animation. I'm storing rlist[P1].gfxbase into a variable before my loop. When the punch button is pressed, i set rlist[P1].gfxbase to my variable + 15360 and then set it back to the variable's value alone after 3 frames. Is there a way to have it reset to the first frame of an animation before it plays? Or is there something fundamentally wrong with my approach here? Any help would be appreciated!
  7. Thanks for the kind words everyone! I did have another question though. I'm not sure how it works with changing sprite animations. Like, say I have an animation where I want my guy to throw a punch. Do I keep all animations on the same sheet and somehow specify which ones to use? If so, is there an in-depth description of that process? The only other thing I can think to do is I would have to have separate sprites for each animation and load and unload them all as needed. Also should I keep all this stuff in this thread or make a new thread for each new programming question I might have?
  8. Ever since I was a kid, I wanted to make a fighting game. I decided to give it a shot with Raptor Basic and have been poking around at it when I have free time (almost never). I had a few hours yesterday to jump back in and got a little bit further along. Keep in mind these graphics aren't final at all. The actual game will look nothing like this. Also there's no actual fighting or collision detection or anything like that yet. You just have a guy that can move and jump around a bit. I think I sorted out my last issues with the scaling that I was stuck on for a while, so I guess that's why I'm stoked enough to make a post about it. When I get something resembling an actual game, I might set up a youtube account or something but for now, all I have is this cheesy cell phone video I uploaded to mega. https://mega.nz/#!dxQUGQKJ!-LPUqbsiJKjvu0_DbeUenVmODidE5B0PwYvcYj0qEe0 I know it will take forever since I'm just one guy but it's fun to work on from time to time.
  9. You probably really should stop doing that, though. Starwander, many thanks for doing this! Just ordered two sets!
  10. That actually looks like it's it. I guess I haven't really looked into the particle layer too much so it's still a bit of a mystery to me. I didn't realize everything on it was relative to the layer's position. I thought they were straight up screen coordinates. That helps a lot, thanks!
  11. I was having an issue with getting the value for the x coordinate located between two sprites. I took the x value for one of them, plus the x value for the other plus its width and divided it by two. Somehow this still seemed to never be quite right and would always look a little off. I plotted a couple of points in a vertical line and set them to the same x value I was positioning one of the sprites at, and it seems to be off. Then to make sure it wasn't something weird with my own code, I tweaked nyandodge a bit and tried the same thing. I added a PX variable to go along with the PY, and set it to some arbitrary value (in this case 40) at the top where I declared it. Then lower in the code, where it positioned the y value, I added this bit. rlist[1].y_=PY rlist[1].x_=PX COLOUR(1) PLOT(PX, 136) PLOT(PX, 135) PLOT(PX, 134) PLOT(PX, 133) PLOT(PX, 132) You can see the results in a screenshot here. My understanding was the the x coordinate of a sprite refers to the left side of it. If that's the case, this line clearly isn't matching up with the left side of that nyan cat. It might be that I don't know enough about how the plot command works or how sprite positions work. If that's the case, could someone talk me through why those things shouldn't line up in that case because I'm scratching my head over here.
  12. It was more a case of I didn't describe the situation accurately and I'm embarrassed to admit I didn't catch it before I posted. At the time, it was so inexplicable that I had no idea what to do. Turns out, I had the wrong variable assignment statement commented out and one of the variables was indeed changing, and at a pretty rapid pace. I didn't look into it enough to investigate why it kept the correct digits at the front. It seems like it ought to have been more random than that but I was just happy to get rid of that whole thing. However, and maybe this isn't the best spot for this and I should start a new thread. There does seem to be some other unrelated weirdness I can't seem to get straightened out. I have a couple of variables for my sprite's x and y coordinates, and sometimes I will print those values to the screen when such information is useful. The problem is that half the time, the numbers seem to jump all over the place. My x coordinate will jump from 100 something to 600 (well outside of the area for the resolution I'm at) and then maybe back down to something else and then at some point return to something expected and normal. The weird bit is, as near as I can tell, my sprite isn't jumping around accordingly. It just keeps moving smoothly and steadily around the screen. I haven't worried about it too much yet since it doesn't seem to actually break anything. I'm sure I'm doing something wrong and I'll figure it out eventually, but does that sound familiar to anyone? On a related note, is there a way to look up and return the current properties of an object such as its coordinates or flip status or scale value or is the only way to do it is manually track that stuff with variables?
  13. I seem to be getting incorrect results when I'm adding two variables together. I'll call them A and B for example. If A=178 and B=296, the answer I get when I add them and store the answer in variable 'C' and print that variable to the screen is 47495680. The first three digits are the correct answer, and no matter what values I set A and B to, the first digits will always be accurate. But it seems to be appending a bunch of digits or multiplying it by some hundred odd thousand or so. There's no other code changing these variables between the time they're set and when they get printed to the screen. Am I running out of memory or reaching some other kind of limitation? Everything seemed to be going well previously... Edit: Disregard. I think I figured it out. But there's no way to delete a post here? Even if it has no replies?
  14. All three of them seem to mostly work now but I still have one minor issue with all of them, that is, the very bottom pixel row of the feet isn't showing up. I'm fairly sure that I have the three frames lined up properly in the bitmap but if I don't, then I'm happy to be told where they're wrong. Or, if it shows up for you properly, then perhaps the issue is in my code somewhere. Much appreciated that you took the time to fix it. I was not expecting any kind of help on that level at all. I thought maybe I'd get a suggestion to use such and such program and export with certain settings (which, if that's what it takes to get working, I'm all for...). In any case, I'm really grateful.
×
×
  • Create New...