Shamus

It would be possible if they existed on the Jaguar hardware. There is only the Object Processor, and its Object List, no character layer, no other kinds of layers.

Personally, I prefer Bad Moodies.

Hey Al, do you have a PDF of the catalog somewhere handy?

Quite. I don't think I even knew this subforum existed until now. And I agree with you on the state of Jaguar emulation, it's still pretty abysmal.

One of the show staff came by asking for vendors to fill out feedback cards and before I could say anything, she said that she was aware of the noise issue and that next year they would definitely address it somehow (I think she mentioned that the bands would be put in a separate room). And as annoying as the announcements were, the bands were by far the largest contributors to the noise factor at CGF this year (and that was true last year as well). So loud you couldn't hear yourself think, and I was situated on the opposite side of the venue from the music stage. Seems to me that the draw at such a venue would be the video game related stuff, not random musical acts! I really hope that CGF staffer was serious about putting the bands in a separate room--that would be awesome.

No, we gave up and formatted our hard drives. In all seriousness, you can play this one (and a bunch of others) at CGF this year, if you happen to be in the Austin area this weekend.

Reboot is going to be there this year with a small booth showing off some Jaguar goodies. Stop by if you're in town.

Wait, what? I thought it was Shane R. Monroe's ring that you had to kiss to get approval.

Actually, the Memory Track is 8-bits only until it copies itself to RAM, then the switches the cart to 32-bit mode in order to access the NVRAM (which lives in the same address space as the cart ROM). It only stores one byte per long address, but it's still a 32-bit interface to it.

It would be much better if you guys could file a bug on the tracker; that way it has a better chance of getting fixed. Forum posts tend to be forgotten after a while.

That's why you should always hold back a few, just so you can put them on eBay and undercut the gougers.

Well, the idea is to get this one out soonish, but there are some ducks that need to be gotten in row ATM. You guys will be the first to know.

Seems that RLN was not respecting the -n (suppress header output) and -l (add local symbols) flags; should be fixed now. New builds of RMAC/RLN are up here: http://virtualjaguar.kicks-ass.net/builds/ Thanks for the report Carl!

Just have to verify what ALN is doing, then a fix will be forthcoming. EDIT: Just having a quick look at the two binaries shows that RLN doesn't seem to honor the -n flag with COF output; also clearly doesn't output the full symbol table either. So should be a relatively easy fix, just have to verify ALN's behavior.

I know that I never used that before, and didn't wouldn't have known what the correct behavior was even if I did. Thanks for reporting this, now I can fix it. EDIT: Can you supply your copy of ALN so I can see exactly what it's doing? It may be that it's not writing the header but writing the symbol table. Also, what was the full command line you were using for ALN?

I would be willing to bet you cash money that this wasn't done by a real live person but by a robot. Youtube's takedown notices work the same way.

The ST version is truly awful.

It was on the side of the board with the cart connector, on the right side near the cart connector. Here's what it looked like: Of course, if you do have that problem, it will probably be on some other part of the board.

Not sure if this will help you or not, but I had some traces on my Jaguar's PCB literally rot out (due to humidity? have no idea really why). I had to solder in some jumper wires to make it work again. So you might want to look at the traces to make sure that they're all good and solid, assuming that all of the other components look good.

If you're looking for an old-fashioned makefile, this is what I use: # Targets TARGET = game64 #==================================================================== # Macro & Assembler flags #==================================================================== # ROM based values STADDR = 802000 BSSADDR = 4000 # RAM based values #STADDR = 4000 #BSSADDR = x MACFLAGS = -fb -g ALNFLAGS = -rq -w -n -a $(STADDR) x $(BSSADDR) #ALNFLAGS = -rq -w -a $(STADDR) x $(BSSADDR) #==================================================================== # Default Rules #==================================================================== .SUFFIXES: .o .s .s.o: ../rmac/rmac $(MACFLAGS) $< #==================================================================== # EXECUTABLES #==================================================================== # NB: Link order is important if you don't specify run address in the linker... OBJ = $(TARGET).o initvid.o $(TARGET).cof: $(OBJ) ../rln/rln $(ALNFLAGS) -o $(TARGET).cof $(OBJ) # cp $(TARGET).cof ../../software/ @-rm -rf $(TARGET).rom @-rm -rf $(TARGET).cof-padded @-rm -rf $(TARGET).U1 @-rm -rf $(TARGET).j64 ../../tools/padcart -a $(TARGET).cof @mv -v $(TARGET).cof-padded $(TARGET).rom ../../tools/jagenc/jagcrypt -u $(TARGET).rom @-rm -rf $(TARGET).XXX @mv -v $(TARGET).U1 $(TARGET).j64 $(TARGET).o: $(TARGET).s enemy-positions.s clean: @-rm -rf $(OBJ) @-rm -rf $(TARGET).cof @echo "Target clean." Of course you would change the paths to various executables to suit your setup.

Do not try to get on the list. That's impossible. Instead, only try to realize the truth: there is no list. Then you'll see that it is not the list that gets written to, but only yourself.