Ad Lunam was a proof of concept, designed to fit into the humble 48K. Here is its big brother, Ad Lunam Plus.



The game is now a 128K exclusive - although I have, as for several of my other titles, considered to make a TR-DOS version which can be run on the 48K with a DivIDE/DivMMC. and ESXDOS - and features graphics for many of its sections and AY sound for national anthems and end-of-game congratulations.


Will you impersonate Von Braun or Korolev?


The main menu

There are other tweakings and enhancements, for instance "pilots" are now aptly called "astronauts" and "cosmonauts" and you can even see their faces when selecting them for training.


Choose an ability to train John Glenn in

In the R&D section, you are now able to see pictures of what you are actually researching.


Soviet research and development main menu


American rockets

Facilities (previously called "structures") can also be seen now, even when they are under construction/repair.


The advanced training facility is being built, while launch pad 1 hosts a rocket for a planned mission

You can now follow missions from the control room.


Engines started, lift off

End-of-turn messages and communications will be shown as papers on a desktop.


The president is pleased with our work

The game is currently at version 1.0 and like its predecessor is available in Italian, English and Spanish. Please report any feedback about possible bugs/strange behavior/typos etc. here or to my email address (shown in the manual).

Enjoy!

Download

Hi,

When compiling programs, using zxbc.py 1.11.1, I get a python warning message:

Not to diss Boride in any way, because it's awesome, but I use Geany already for other things, and was wondering if anyone had given thought to adding a zxb plugin?

Never made one, so it could be trivial, or a pain!

I'm using Boriel 1.9.8 (I think) on MacOS 10.15.4 with Python3 (version 3.7.7, installed via HomeBrew). I'm invoking Boriel thusly:

Quote:/Users/mauvedeity/bin/zxbasic/ply/lex.py:760: FutureWarning: Possible nested set at position 10
  c = re.compile('(?P<%s>%s)' % (fname, _get_regex(f)), self.reflags)
/Users/mauvedeity/bin/zxbasic/ply/lex.py:498: FutureWarning: Possible nested set at position 274
  lexre = re.compile(regex, reflags)

Team,

When I use the library, the screen scrolls, however the colour of the objects bleeds to the background colour.
Is there a fix for this and also the x,y,x1,y1 cordinates of the scroll window don't seem correct.

Thanks for looking into this as I am desperate for a scroll function. thx

Hello all,

I'm pretty new to ZX Basic so please forgive my possible beginner questions.

I'd like to pass an Array to a Sub but cannot seem to figure out how.

Hallo Jose. When I try to go to the ZXBC Wiki from your site, it is down. Any chance to bring it up again? I want to finish the help in BorIDE. are there new commands? added? (hint: like SWITCH/CASE)?

Will we see Zx basic compiler compatible with the next????

Hi   
This little program should work or am I missing something?

If I compile it gives error

Hi   

I tried the print64 routine but has a bug 

If you try this program in red

#include <print64.bas>

'printat64(10,10)  'This will not work because de poke is incorrect You can try
print64("Hello world!")

print at 15,0;"@p64coords "; @p64coords;


and then you look at the dissasembly attached image

where after the RET with red color in the image, is supposed that is the @p64coords address (when you run the program writes the @p64coords address to check where is)


in this @p64coords address is where is supposed to poke de X and Y values of the new coordinates with the printat64 routine that is included in print64.bas

but the coordinates are in the green lines addresses with the value 12 and 0 

you can check this if you look at the same time at the image with colors ( or your own dissasembly) and the print64.bas file

There is some bytes in between that are moving down the useful poke for the coodinates that  printat64 routine does


ANOTHER THING
----------------------------------

This bug was found because i was trying to change the print64 font to another one

I did this subroutine for this

' Changes character set of the print64 routine
' this does a poke where is the assembly instruction :      ld de, p64_charset
SUB change64Charset (new64CharSet as uinteger)

       poke uinteger ( @p64coords - 123 ), new64CharSet

END sub


Maybe you can solve the bug AND  at the same time include this subroutine in the print64.bas file

this way the people can change the print64 x,y  and the character set of the print64

i named the subroutine change64Charset but you change the name accordly to the print64 routine

i don't know for example  print64ChangeCharset or something

you can only must be sure that the poke is always made in the correct positions for both routines

i don't know if is posible to include some constant label inside the routine that makes some positions of memory fixed to be poked

Now we must calculate by hand until fixed someway, where are the addresses to poke

if you try this subroutine adding 7 to the original subroutine it works  

SUB newPrintat64 (y as uByte, x as uByte)
    POKE @p64coords+7,x
    POKE @p64coords+8,y
END sub