Jump to content
Jagware

Zerosquare

Administrators
  • Content count

    2,138
  • Joined

  • Last visited

  • Days Won

    5

Posts posted by Zerosquare


  1. joli effet de flamme par contre j'ai mal à le tête maintenant Oo :'C

    :)

    [Français]

    Ouais, pour le scroll, vaut mieux pas être trop près de sa télé ! :)

    Sinon, encore une fois ça marche parfaitement sous Project Tempest :yes:

     

    [English]

    Yeah, you shouldn't be too close to your TV while watching the scroller ! :)

    Otherwise, it works perfectly under Project Tempest once again :yes:


  2. [Français]

    GT Turbo m'a pris de vitesse, voilà donc la démo de 1376x576, toujours en 50 Hz et à charger en $4000. Branchez votre télé en RGB si vous le pouvez ;)

    (Désolé GT, je ne pense pas pouvoir aller plus loin, c'est la limite du hardware !)

     

    [English]

    GT Turbo has been faster than me, so here is the 1376x576 demo, still in 50 Hz and at address $4000. Connect your TV set using RGB if you can ;)

    (Sorry GT, I don't think I can go further, this the hardware limit !)

    HiResDm2.zip


  3. regarding "OP interlace bug":

    there are a number of ways to make this:

    --set dwidth to twice the size of the picture, but only display width pixels... then each vbl change the start position of the first pixel.

    (the one i used)

     

    --The 2nd a bit more "hacker style" woudl be to do a pre-processing of the picture separating the odd&even lines into two pictures "on top" of another..

    So 1st picture (say 640 width.. and also dwidth) only contains even lines... the secound picture (640*480*2 bytes away in memory) contains the odd lines...

     

    THEN! ..you could actually utilise the other OP bug in your favour and you would only have to update the height variable in the OPL every other vbl! =)

     

    Hence saving OPL update time!...

     

    Thats the hacker way to do interlace :)

    Funny, I see we're thinking along the same lines ;)

    I used the first trick in the demo, just as you did, but thought of the second one afterwards.


  4. Thanx for the email zerosquare..

     

    ..hmm my routine had the same kind of "flicker" in the text.. I guess it is because the text is so thin.

    Guess interlace gfx needs to be made with some restrictions...to not flicker that much.

    You're right, it's not a problem with the code or the Jaguar, it's an inherent limitation of interlacing. Video cards with TV-outputs use a vertical "smoothing" filter to alleviate the problem, and computer-generated graphics for TV broadcasting are made with this in mind (images from video cameras are usually OK as-is, since they rarely contain sharp vertical edges).

     

    Some thoughts:

    --Hmm i never tested my rout in 60Hz, but it also didnt work.. ?.. was a bit surpriced.. since the method has nothing to do with the framerate, so i kind of assumed it would work.. but did not..

    So if someone wants to make a "European game ONLY" then here is a way to do it =)

    It needs to be debugged in 60Hz to se if it is possible to do Highres on an US jaguar...

    There are 525 lines per frame in 60 Hz instead of 625 in 50 Hz, so a few values have to be modified. Not tested it yet, I need to locate a 60 Hz-ready TV set first :)

     

    --It is said that the OP in interlace mode skipps every other line.... but that i never got to work, so i worked my way around it.. what about you?

    Same thing. I guess that's either an error in the documentation, or a bug in the chip (Atari didn't seem to care much about interlacing, so maybe they had not tested it extensively).

     

    --and then there is that "interlace vbl irq" thing... but that i guess you figured out ;) ... (i dont understand that eor you do but aparently it works =)

    So you disassembled my code, uh ? :D

    Sorry then for the horrible coding style (recycled Atari example + first 68k code for me).

    The EOR is just a quick way to toggle between two different values :)

     

    regards

    /Sym

    Thanks for the comments !


  5. so, the jagwire has 2 plug, one for the jagpad and another one for the JagCF ?

    Yes.

     

    is the JagWire more stable on WinXP than the Dos BJL software under portalk or whatever parallel port winxp driver ? (I hope so ^^)

    Much more, it seems. As of now, I've not had a single failed download using the JagWire. :)

     

    since it is compatible without using a JagCF, will the JagWire be available before the JagCF release ?

    if yes, when do you plan to release it ?

    Yes, it will be available before the JagCF release, but we don't have determined a definite release date yet.


  6. [Français]

    Voilà une petite démo d'image en 688x576 ; pour le moment, ça ne fonctionne qu'en mode 50 Hz.

    Le code est assez mauvais, je le rendrai dispo quand il sera nettoyé. :)

    EDIT : certaines personnes ayant eu des problèmes avec le format COF, j'ai rajouté une version en .BIN (à charger à l'adresse $4000).

     

    [English]

    Here is a small demo of a 688x576 picture ; it only works in 50 Hz mode for the moment.

    The code is rather bad, I'll release it once it is cleaned. :)

    EDIT : some people have reported problems with the COF format, I've added a .BIN version (upload at address $4000).

    HiResDem.zip

    HiResDem_bin.zip


  7. Well... :blush:

     

    I just checked that changing this register enables the generation of a proper interlaced video signal, using the code for a little demo from SCPCD as a framework...

     

    BUT ;)

     

    Displaying a high-res picture was my next step. I started playing with it yesterday night, but as this is my first piece of code on 68K and my first attempt at Jag programming, you can guess I'm a bit slow :P

     

    So you are most probably right about it being more complicated than setting a single register.

     

    Enough chatter... more code awaits :)


  8. And the answer is (for 50 Hz) :

     

    move.w #624, $F0003E

    ($F0003E is the Vertical Period register)

     

    I thought it couldn't be that simple (since almost nobody seemed to have done it before), so I spent several days searching information about video signals, and deciphering Atari's documentation... but that's it, and it works. ;)

     

    Nothing wasted, though ; now I understand how to setup all the video registers, so if we need to tweak the resolutions, I can do it :)


  9. [Français]

    Questions aux pros de l'Atari : le port série monte jusqu'à combien en vitesse ? Est-ce qu'il supporte le contrôle de flux matériel (lignes RTS et CTS) ?

     

    Le circuit de gestion USB du JagWire fait essentiellement la conversion USB <-> série, donc il y a moyen de le remplacer par un simple convertisseur de niveaux (genre MAX232) pour pouvoir se brancher sur un port série classique. Ça sera sûrement moins rapide, mais ça marchera.

     

    D'ailleurs, les Ataristes ont-ils vraiment besoin de la partie BJL, qui semble déjà marcher correctement pour eux sur port parallèle ? Ça vaut peut-être le coup de faire un autre petit module dédié JagCF...

     

     

    [English]

    Questions for the Atari specialists : what is the maximum speed of the serial port ? Does it support hardware flow control (RTS and CTS lines) ?

     

    The JagWire's USB chip is essentially a USB <-> serial converter, so it can be replaced by a simple level shifter (such as the MAX232) to allow the connection to a standard serial port. It will probably be slower, but it will work.

     

    By the way, do the Atarists really need the BJL part, which seems to work fine for them using the parallel port ? It would maybe be interesting to create another, JagCF-only add-on...

     

     

    Je soutiens Zerosquare à 200% dans ce projet ! :)

     

     

    [english]

     

    I'm a Zerosquare fan :)

    [Français]

    Merci FrediFredo ! :hug:

     

    [English]

    Thanks FrediFredo ! :hug:


  10. [Français]

    En jetant un coup d'œil au schéma de la Jag pour trouver comment utiliser le mode entrelacé, j'ai découvert un truc bizarre : la sortie B0 de Tom est reliée à un point de test, et l'entrée B0 du DAC vidéo est reliée à la masse, ce qui veut dire qu'il n'y a que 7 bits de résolution affichés pour le canal bleu (au lieu de 8) :huh:

     

    Atari nous a-t-elle menti à propos des 16 millions de couleurs, ou est-ce que c'est une erreur sur le schéma (ou une version préliminaire) ? J'ai la flemme de démonter ma Jag maintenant pour vérifier -_-

     

     

    [English]

    While peeking at the Jag's schematic to find out how to use the interlaced mode, I found out something weird : Tom's B0 output is connected to a test point, and the video DAC's B0 input is connected to ground, which means there are only 7 bits of resolution displayed for the blue channel (instead of 8) :huh:

     

    Did Atari lie to us about the 16 million colors, or is it a schematic error (or a preliminary version) ?

    I'm too lazy to take my Jag apart now to find out -_-


  11. [Français]

    Merci pour la pub ^_^

     

    Quelques précisions :

    • Il y a deux modes d'utilisation du JagWire : le mode BJL classique, en remplacement d'une connexion à un port parallèle, compatible avec la ROM BJL, la cartouche Protector:SE et le CD BJL (donc utile aussi à ceux qui n'ont pas la JagCF) ; et un mode de communication rapide avec la JagCF (jusqu'à 3 mégabits par seconde).
    • Les logiciels seront fournis avec les sources, et compatibles avec (au moins) Windows 9x/2000/XP et Linux.
    • Pour l'upload de Native Demo, ça prend en fait 19 secondes B)
    • Pour le moment, ce n'est qu'une version bêta, il va falloir un peu de patience :blush:
    [English]

    Thanks for the publicity ^_^

     

    A few precisions :

    • The JagWire has two modes : the classic BJL one, to replace a parallel port connection, which is compatible with the BJL ROM, the Protector:SE cartridge, and the BJL CD (therefore, also useful to those who do not own the JagCF) ; and a fast communication mode for the JagCF (up to 3 megabits per second).
    • The software will be provided with sources, and will be compatible with (at least) Windows 9x/2000/XP and Linux.
    • Uploading Native Demo requires about 19 seconds, in fact B)
    • It is currently a beta version, so you will need a little patience :blush:

  12. Hi ray,

     

    I unfortunately can't offer advice since I never used GCC on this platform, I just wanted to tell you might have to wait a bit for others to reply, since :

    • Most of us just came back from the Atari Connexion 2006, so we're still a bit tired ;)
    • AFAIK, the majority of coders here only use pure ASM, so they probably won't be able to help either (don't ask GT Turbo what he thinks of C, for example :P )
    BTW, I saw your group's demo (the one with the sung lyrics) at the AC ; I was really amazed, it's truly an art piece :yes:
×