Forum Comments

Scroller Games?
In Ask For Help
NESmaker Team
Test
Test
Mar 14, 2022
The NESmaker forums are at www.NESmakers.com. This site is not the NESmaker forums. The NESmaker forums have hundreds of active users. The FB group, despite you having an aversion to it for whatever reason, has thousands of users who are eager to help. This isn't really a forum, it's a back end channel that exists for thread comments on the news page and whatnot. Very very very few people (literally, one or two) have used it as a forum. It is not checked, and if it ever is, there are only one or two people who would check it. The link above will give you broader access to more people. A lot more. A trackball is not a officially supported peripheral of NES games that I know. A trackball sends information to the device. The NES controller ports read bit information from devices. I am sure that a trackball could be set up to effectively give you dpad data, and likely someone has done this, but it is not something we have done, nor any of our users. You're really asking two things: 1) How can I do something with a very specific peripheral for the NES 2) How can NESmaker utilize that data. For the former, that's the part you'll have to dig into outside of NESmaker's default code base, since there is no one who has done this before with this code base. There is no tutorial that exists as to how to take trackball data and use it in NESmaker, because no one has tried to take a trackball and use it in NESmaker.. How does a trackball send information, and how can that be turned into the information that a NES gamepade sees? That is engine-agnostic. It has nothing to do with NESmaker. That is a hardware thing. It would be the same if you were coding from scratch, using NESmaker, or using any other library. The first thing to do is to figure out how to get trackball data to a NES port, what that looks like to the NES (likely being passed by the registers that, in nesmaker, populate the gamepad variable). For the latter, this is what you'll need a good handle on how NESmaker works to accomplish. My advice has been, and will continue to be, this sounds like it's the game you truly want to make, but you're not quite there yet as to how handle that logic from within NESmaker. No problem - as expressed already, the thing you should really do (ask any NESmaker user who has had this problem) is do a bunch of burner projects unrelated to this one. LEARN how the software works. LEARN how it works with the underlying ASM. Start getting your hands dirty there. Then, the integrations you're talking about will become more sensible, AND you'll understand how to play around in that proverbial sandbox - as in, you'll know what to do with that trackball data (step 1 - non NESmaker question) to make it do things in NESmaker (step 2, contingent on understanding how NESmaker works). I hope that helps!
1
0
Scroller Games?
In Ask For Help
NESmaker Team
Test
Test
Mar 09, 2022
Hey there Kevin - Short answer - make sure that you have the latest version of the software from the site (looks like you do, I think). The tutorials on the LEARN page of the website are up to date, and will always be up to date. If you have a fresh install of 4.5.9 (fresh from when it was updated, two years ago - date on the site), that version will work perfectly complementary and have included everything you need for those tutorials on the LEARN site. The reason you see SCREEN FLAG 2 rather than some specific label like "scrolls to the right" is that those 8 "Screen Flags" are dependent on the module. For instance, if you're making a top down adventure game, you don't want to waste a precious bit of data on clicking on scrolling, since there is no scrolling camera in that module. You could make that bit flag do ANYTHING you want it to do in code, which you can see in the more advanced tutorials, and therefor you can NAME it anything to go with whatever YOU use it to program, should you get that advanced. The modules have bit flags that work with their respective collision/physics/camera systems, and the labels are saved with the modules/projects. So if you are seeing "Screen Flag 2", that means that you don't have a module loaded up that has given that a name. Again, to be clear - a fresh install of 4.5.9 will have all the modules found in the TUTORIALS from the LEARN page, which are the only tutorials you should be looking at, especially if just getting started. Also, make sure to join the NESmakers fb group / forums, as there are LOTS of eyes there and people very anxious to help newcomers get up and running!
1
0
N
NESmaker Team

NESmaker Team

Admin
Test
Test 2
+4
More actions