Search the Community
Showing results for tags 'atarix'.
Found 2 results
Hello everyone, Today I've released the first Work in Progress video for the AtariX IDE I've been working on. The video showcases some of the tools in the IDE, like the Playfield Editor and the Object Editor, also the HUD which allows you to pick a font and a color for the 6 Digit Score. Next thing I'm going to work on is the LOGIC part of the Object Editor, which will allow developers to add properties to the object (like collisions, input etc) without having to write a single line of code. The main goal of AtariX is to help newbies to get into Atari game development and also for advanced users to build some prototypes, so you can export the Assembly code and add more advanced stuff into your game. If you have any thoughs or ideas, please let me know.
Hello everyone, I'm a beginner on Atari programming and I'm creating an IDE to allow people to create Atari games without having to write a single line of code. I'm learning Assembly as I go through the IDE and add more stuff, it's helping me a lot. This is what I've got so far: A simple IDE that lets you draw the playfield and change the color of both playfield (COLUPF) and background (COLUBK). If you hit the "Play" button, it will produce the following result on an emulator: This also generates an assembly code file, please take a look at this file to help me with the questions: atarix_result.asm So, considering I've read a few articles about programming, I've come to a conclusion that every single line of code matters when you're programming for Atari. So I would like to ask a few questions: 1. Looking at the file (atarix_result.asm), is the generated code bad? What optimizations should I look forward? How can I optimize this code? 2. What kind of things should I avoid when drawing to the playfield? 3. Also, is there a way to get rid of the parts showed on the second screenshot? (Where the arrows point at). Or is this an expected behavior? Thanks!