SebRmv

Are these four images correct?

(these are ASM files, to include in a source file)

space.zip

One possible solution for you Windows users is possibly to install a linux distro on a virtual machine (eg Virtual Box).

It depends on the fact that your own PC is recent/powerful or not...

Could be fun, indeed.

Subsidiary question: how to view CRY15/RGB15 picture on a Jag?

I naively thought it was just needed to add VARMOD when setting VMODE, but it does not seem to work as I expect...

As said above, the problems are only in CRY16 mode - other modes produce valid files.

so it is really CRY16 mode? I would have said that it is CRY15 which is buggy (clearly, there is a mistake in it since pixel value is always ORed with 0x1 in this case)

Further note - *both* your convertors *always* get the first word in the file wrong (pixel 0,0).

 

eg, give it a pure black bitmap, and the entire file will contain a single repeating word, with the first word +1 intensity.

 

Hope this helps.

When you say "always", does it really mean always or is it only for CRY 16 bits?

is there any CRY viewers on computers? or should I test on a real Jaguar?

just to be sure I have understood correctly, the command that produces a wrong result is:

./converter.opt -cry --16-bits space.bmp isn't it?

but

./converter.opt -cry --15-bits space.bmp works fine?

Note: I would be less surprised if it was the contrary...

Ok, I'll investigate that, maybe at the AC next week-end

tout pareil, bon anniv les frèrots

Do not forget also

Diamjag

Atomic Reloaded

Great!

Joyeux anniversaire Odie!

Great work guys!

While surfing on Reboot website, I wanted to download PROJECT1.ROM but unfortunately, the link seems to be broken. Could you repair that?

Pour les programmeurs, la page d'Another World donne une bonne idée de ce à quoi ressemble le langage de scripts.

J'ai un peu des doutes sur le fait qu'on ait vraiment envie de programmer dans ce langage...

Bah a priori, oui c'est tout à fait envisageable...

sauf qu'il faudrait recoder les outils de développement qui vont avec car sans, ça me parait un peu hardcore.

(en particulier un éditeur de polygones et un éditeur de scripts)

Aussi, plutôt que d'utiliser exactement la même machine virtuelle (ie le même langage de scripts), j'en profiterai pour

corriger certains aspects du langage avant de m'en servir pour un nouveau jeu.

Ah oui, another world est maintenant adapté sur jaguar, il sont partis d’ une version existante si je crois avoir compris.

La conversion est donc plus facilement envisageable qu’ une création pure et dure?

Hello,

et bienvenu sur le forum.

Concernant le portage d'Another World (puisque c'est moi qui l'ai fait), on avait certes les sources ASM 68k qu'Eric Chahi nous avait donné

mais je suis finalement reparti de zéro et j'ai réécrit en C toutes les parties non critiques et en ASM GPU et DSP les parties critiques (dessin de polygones, son).

Donc il ne s'agit pas "juste" d'une recompilation dans le cas d'Another World.

Mais dans ce cas précis, le portage a été finalement assez facile à faire car le jeu lui-même est écrit dans un langage de script: il a donc suffi de porter la machine à interpréter les scripts (ce qui inclue quelques routines graphiques

et sonores)

Note: le jeu est porté (il reste un peu de finition à faire, surtout concernant le son) mais pas encore diffusé...

Well it could be nice documenting the things I learn about the Jaguar and write them down somewhere. If you allow this, I can start from quoting the official Atari docs and then refining them as I go along.

Why not? This could be a good start, even if it infriges a bit the "do not submit copyrighted work" policy.

If I remember correcltly, you wan ask for an account directly on Jagopedia website. I'll validate your subscription afterwards.

(Otherwise, we'll see by PM maybe)

(OT: maybe it would benefit all to make a semi manual/semi tutorial doc for the blitter? I.E. Explaining in simple words what the registers do and some sample programs like "if you want to do ....., then use this source as base)

That's what I planned when I started Jagopedia (http://jagopedia.atari.org)

If you wish to contribute, I open an account for you.

By the way, you may be interested by looking at the source code of the renderer I have written for my library.

I have learnt a lot of things about the blitter while doing this (especially Gouraud/Zbuffer/...)

Unfortunately, I am too lazy (for the moment) to rewrite a more efficient a renderer (ideas are written on paper though).

Nice to hear that it helped you!

Good point CyranoJ regarding the original tools (I am a very conservative guy by the way... I tend to use original tools or config whenever I can)

I'll have a look at your setup in the next days.

I just tried it and I could compile it after a few changes. However the gcc doesn't support dos.

Which means using dosbox for linking and windows for compiling and at the same time keeping all library files in the project folder, which is kind of annoying at the moment.

 

I hope we find a better way to do it, maybe support for the .a file could be added to sln? No idea how much effort it would take though.

 

Also, keep in mind that dos only supports 8 symbols + 3 symbols extensions. in other words files like interrupt.o need to be renamed.

Yes, for the moment, it is not really usable, but it is the fault of aln.

How the hell can you use these tools on Windows?

Has someone managed to get the latest sln version from Subqmod website?

Maybe the support of *.a files has been added.

In theory, aln uses the environment variable ALNPATH to look for libraries.

However, I can't manage to define/read environment variable in dosbox.

I tried:

set ALNPATH=c:\jlibc\lib

echo %ALNPATH%

and the "echo" says "%ALNPATH%" instead of the expected result.

Ok, the right command line (on DOSBOX) is

aln.exe -a 4000 x x -rq -v -v -v -w -e -o example4.cof crt0.o example4.o data.o display.o interrupt.o sound.o rmvlib.a jlibc.a libgcc.a

(I assume that everything is in the same path for simplicity... next step will be to indicate the different paths to ALN)

one issue with dosbox is that the size of the command line is limited (the line above is too big!)