GreenNerdyFrog Posted June 17, 2020 Share Posted June 17, 2020 Hello everyone, I've decided to start coding for Atari 2600 and as you can guess I have encountered some beginners problems. So where am I at this moment? I have downloaded latest Batari Basic (bB-1.5-win-x64) and installed it. I have downloaded latest VisualbB and Stella. After configuring VisualbB and writing first simple code, I have encountered problems with compiling my game in VisialbB. Code for reference: playfield: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ................................ ................................ ................................ ................................ ................................ ................................ ................................ ................................ ................................ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX end COLUBK = $CA COLUPF = $C2 draw_loop drawscreen goto draw_loop VisualbB after pressing "Compile" button outputs: " Compile started at 17.06.2020 14:44:21 Compiling C:\atari\AtariProjects\manthatjumps\default.bas " But no *.bin file is created. After some tinkering with VisualbB and Batari Basic, I've decided that code can be compiled using 2600bas and compiled the game. "C:\atari\batariBasic\2600bas C:\atari\AtariProjects\manthatjumps\default.bas" Output: " batari Basic v1.5 (c)2020 2600 Basic compilation complete. 2768 bytes of ROM space left " And the game worked in Stella. But still I cannot lunch it through VisualbB. Error message: " [17.06.2020 14:46:21] Could not locate default.bas.bin. Attempting recompile... Compile started at 17.06.2020 14:46:21 Compiling C:\atari\AtariProjects\manthatjumps\default.bas " File is in proper catalogue after compilation but VisualbB or Stella(when I want to start it through VisualbB) does not see it. How can fix my VisualbB and get it to work properly. My operation system is Windows 10. I have already: Change all the paths to not contain spaces or polish signs like ż,ś,ć etc... Tinker with Batari Basic Run VisualbB with different older system compatibility options (This never worked for anything for me to be honest) ALSO! I have problems when compiling following code using cmd console: playfield: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX ................................ ................................ ................................ ................................ ................................ ................................ ................................ ................................ ................................ XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX end COLUBK = $CA COLUPF = $C2 player0x=30:player0y=30 player0: %01011010 %01011010 %01011010 %01111110 %00111100 %10011001 %11111111 %00011000 end player1: %10000001 %01000010 %00111100 %00111100 %00111100 %00111100 %01000010 %10000001 end draw_loop drawscreen goto draw_loop Output is " batari Basic v1.5 (c)2020 (18): Error: Unknown keyword: = Compilation failed. " After deciding not to compile using VisualbB, I cannot proceed anyway. ? Maybe someone more knowledgable can help me and point me to proper tutorials, solutions etc that can help me get started. P.S. Yes code is from Tinkernut but I did not use his installer for software. Quote Link to comment Share on other sites More sharing options...
+Karl G Posted June 20, 2020 Share Posted June 20, 2020 On 6/17/2020 at 9:05 AM, GreenNerdyFrog said: player0x=30:player0y=30 I'm not seeing an intention on this line, which is probably the cause of your error. I don't have anything to offer as to your issue with Visual bB, but I would recommend that you try using Atari Dev Studio instead. The former was abandoned years ago, and the latter is still undergoing active development. Quote Link to comment Share on other sites More sharing options...
GreenNerdyFrog Posted June 22, 2020 Author Share Posted June 22, 2020 Thank you for the reply Karl G. That's exactly what I have done and it works perfectly. Now I'm using VisualbB only to create sprites, playfield, etc. On 6/21/2020 at 1:20 AM, Karl G said: I'm not seeing an intention on this line, which is probably the cause of your error. That was the problem. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.