Jump to content

philipj

Members
  • Content Count

    927
  • Joined

  • Last visited

Community Reputation

244 Excellent

About philipj

  • Rank
    Dragonstomper
  • Birthday 03/11/1977

Profile Information

  • Gender
    Male
  • Location
    Birmingham, Alabama
  • Interests
    New Developments for classic Game Consoles.

Recent Profile Visitors

14,901 profile views
  1. It's funny the 7800 is mentioned... the "Maria" graphics chip on the 7800 is able to read display list supper fast until the main processor slows things down especially when it's accessing the "Tia" sound chip... It was always my assumption that similar principles apply on the Jaguar when the Motorola 68K accesses the BUS slowing the other processors down when in use "Hogging the BUS".
  2. Well... It had a 64bit programmable Blitter; not neccessarily a full fledged processor in the truest since, but can be controlled by any of the other 32bit processors... According to Atari, because of the Blitter being 64bit sitting on a 64bit BUS, "The Jaguar is 64bits when it needs to be and 32bits when it needs to be" with the "Motorola 68000" to give the programmer a "Warm and fuzzy feeling..." for those who are familiar with just programming with the M68K... One could just use the Motorola and the Object processor to just make 2D games thus it would directly compete with the SNES and Genesis that way.
  3. Well I'm thinking more exclusively for Jaguar 3D development more than anything else... I think it would merit some effort using the Jag for that purpose. I think Atari had a missed opportunity with the Jaguar and ST... Certainly with the lower 520ST computers, I think interfacing the ST with a Jag for commercial use back during the system's hey day would've been nice. Man it's been years since I used "GMAX" or 3D Studio... I remember "MilkShape... It was some kind of 3D modeller for low polygon 3D objects that were used in games for the original XBOX and PS2; at least the older version was. That stuff brings back fond memories when I was at VC for CAD, but they also had a lot of computer animators and 3D modellers there using those big black "Alienware" computers. I was very fortunate enough to take up some 3D modelling although I never master texturemapping and I pass lighting class by the skin of my teeth... Still very fun times back then.
  4. Here's something interesting I had in my "YouTube" archives... It was "SYMBOLICS" 3D software package that would later be used for the "Nintendo 64"... It was possibly used to make "Super Mario 64", which just completely turned the gaming world upside down at the time of its release... It would've been great if the Jaguar had something similar that could handle those kinds of graphics... Very cool stuff in my opinion; I'd love to see something like this on the "Atari Jaguar" for 3D game development.
  5. Well... Sigh... I've spent a lot of time thinking backwards and forwards about how the Jaguar works, but never really implemented any kind of game development... QBASIC was a language I ran into some years back on an old "IBM 486 PC" I had in the mid 90 I never really fully understood so QB64 seems to be a bit of a second chance at the language...? I have some history with the old language running the executable including that came with the package; can't really think of a better language to try and grasp the concept of making games and what it takes to make them well... I can't help but feel like it's all talk at this point, but that's where my head is right now I'll probably eventually get to the tools yall have made, but for now, I have too many other priorities in real life and family that seems to take a lot my attention these days... I'm just going to have to force myself at the compiler at some point. Yea I got a lot of old documentations on much of that... I know the DSP has a 16bit interface on it even though it's a 32bit processor... The GPU jumps from internal cache to main ram, I hear you have to be a bit lenient on the GPU accessing main unless wind up hammering it where you can literally fry an egg on the chip using a consistent loop or something to that affect. That's another experiment sitting on the back burnner for another time... I think it's important at this point in time I just focus on the game; also I got hard copies of this book that discusses making real time 3D on the Atari ST in "Assembly", which I've chosen to be my Assembly language trainer to help head me in the right direction... It doesn't matter if I use the 3D engine in the book or not, what matters is getting an understanding on 3D programming in Assembly Language; that's the ultimate goal.
  6. I actually had the game in my N64 library before I sold it on ebay some years back... Was supper impressed with the game and the digital music coming from the sound chip... Kudos to the music composer.
  7. Yea that's true... Still I'd like to know how some things are done for future use... Was just looking at "Virtua Racing" was done on the "Sega Genesis" and it appears that both VR and "Starblade" shoot sprite pixels to the Geny graphics chip to be displayed very quickly... If there's a way to get the Jag to do fast 3D that's very natural to what the system was originally designed to do, then yes I'll always keep an open mind to those things. I consider it a little fun to brainstorm those things no matter how crazy the idea, but you're absolutely right I should just focus on game making instead of all of this other stuff.
  8. Yea but wouldn't the Motorola and DSP have better access to main ram...? I guess the GPU would have it as well, just can't make jumps from internal cache to main ram... If that's the case, then yea the GPU is probably the only chip I need to work with-with main ram being the slower memory to use in comparison to the GPU internal memory. I never really agreed with the notion of just cutting the 68K off completely for the other processor, but that's another issue entirely. That's one of the reasons I choose to learn QB64 so I can just focus on making games without the hardware restrictions and worry about that other stuff later...
  9. Yep... Same speed as the 68K on the Jag... I could've given too much thought on Namco pulled off the graphics on the Sega CD... with the screen resolution being smaller than the average FMV on "Starblade", it's quite possible that uncompressed sprites/stamps are being streamed directly to the Genesis video chip. The Sega CD has 700KB of memory set aside for storing CD data, which is a very considerable amount of memory to work with if used in the right way; Sega originally was going to use 1MB of memory, but instead ran with the 700KB to cut cost. The Sega CD seems like a great little well rounded system to study, draw inspiration, and pull ideas from without all of the bugs that the Jaguar has, but can use (learned concept) in similar fashion.
  10. True that... Really FMV should've been more of an 80s thing with games like "Dragon's Lair" and such instead of coming out in the late 80s/early 90s like it did... It seem like some of those FMV companies were trying to make up for lost time and lost profits, but that's another story. "Starblade" for the Sega CD was rumored to have used both polygons and FMV on the to pull off 3D graphics; the game was made so well it was somewhat hard to tell which one was FMV or which one is real polygons. Personally I think the wireframe objects in the game are the real polys and the rest are some kind of FMV or some kind of streaming data from the CD... It's possible they could've used the Sega CD extra hardware to stream background polys while the Genesis render the wireframe stuff much like what "Silpheed" did; of course the background for that game was most likely all FMV with the Genesis rendering the playable 3D low-poly 3D spaceship objects in real-time including the bosses (except the final boss and one other boss).
  11. The "Jaguar" is obviously more powerful than the "Sega CD", but there's one thing I admire about the Sega CD unit and that's the ASIC chip that allows for fast scaling and rotating sprites much like the Jag's "Object Processor"... Of course they work differently, but they both handle sprites in similar fashion with the OP being the more advanced processor.
  12. Battlesphere was one of the only games that worked around the Jaguar's encryption... think that might have something to do with it not working correctly? Might not be the same deal with "BS Gold" where the encryption keys were available to the public around the release date of that game... Just a thought; I could be wrong.
  13. VladVR was one of the few to tackle 3D on the Jaguar... Very admirable if you ask me... It's too bad the game never came along further. Despite the polygonal look, I think the game gets a pass for being a home-brew... As long as the game-play is good, I've played a lot of bad polygonal games that were very fun to play and thus got a pass on being so blocky. Too expect too much more from the Jaguar would require pulling some tricks beyond the normal, which is what I'd like to do someday... Until then, you have to settle for what you can get out of the Jaguar system.
  14. That's kind of unfortunate about that... The demo VladVR was not too shabby in my opinion... One thing about all of 3D stuff on the Jaguar; the more I look into what the Jag can actually do with 3D versus what I'd like to see it do, the more I'm starting to look closer at more of a 2D pseudo 3D rout in classic form that looks more appealing with faster gameplay like "Super Burnout" for the Jag using sprites. Maybe one day I'll find a way to trick the Jag system into producing fast 3D using 2D methods; that has always been my philosophy concerning the Atari Jaguar and that's its ability to produce fast pseudo 3D on the fly thus the art of faking 3D. A couple of games come to mind... "S.T.U.N. Runner" for the Atari Lynx and "Night Striker" for the Sega CD as great futuristic sci-phi racers using scaling sprite based graphics... I haven't personally played "TUBES" yet on the Jag, but it seems decent enough. I've always considered "STUN Runner" to be another version of "RoadBlaster" redone in 3D with a different vehicle mechanic.
  15. Nintendo basically did what Sega did by going to an industry standard when they made the N64 back when Mario would make appearances on electronic bill boards in basketball game as a real-time CGI; they basically went the way of SGI (Silicon Graphics) type technology IMO... Same way with Sega when they created the "Virtual Racing" arcade game, however it seems like Sega was trying to do their own thing based on the "sprite based" arcade games that they were already doing with such games as "Out Run, Space Harier," and so-on thus the Saturn hardware seem to reflect some lessons from those proven technique. The good thing is that the "Atari Jaguar" seems to be right on the heels of the kind of graphics Sega was producing with the "Object Processor" originally designed for the Panther... I can go on and on about that sort of thing so forgive me if it seems like I'm coming out of the blue. The only problem with the Atari Jaguar is the "Video RAM" or lack there of in comparison to systems like the "3DO, Sega 32X (which has less RAM then the Jaguar, but better access to more memory than the Jag), and the Sega Saturn" which has more than enough video memory to give the Playstation 1 a run for a short time.
×
×
  • Create New...