omf

1, you would need to handle this yourself, i do not believe there is any functionality to do this automatically 2, you could probably add or subtract 1to the scale sections of the object list. NOTE: scaling objects leaves the collision box as it is. you need to scale that separately. use my list editor for the correct scaling values 3 you would need to control this manually, setting the gfxbase to the required address to the frame you want, there are a few examples of this going around, if you wan find any then i can provide something

you may also want to look at my object list editor, it allows you to integrate the object lists into your code very easily, it also allows you to make changes extremely quickly, this includes moving the objects up and down the list with a simple mouse drag, look at the version here on AA if you like it, there is a newer version, if you want it after testing pm me

you you might try examining the crystals, one may not be connected on one of the pins, a crystal that is connected by only 1 pin is rather useless and will give you a permanent black screen. you may have hit it by mistake when doing the mods you have done , failing that you have probably damages a board trace so that it is not connected, inspect all the ram chips and make sure that all pins of the chips can be reached by the joining traces, so test at the other end of themand the chip pin leg

as the netlists for those chips exist, it is theoretically possibly to create another batch of these i have no idea how hard a task that would be or if the netlist files are the latest ones in existence either

can i just point out that an eeprom either 93lc46 / 93lc86 is a relatively tiny priced item and would have been $3 absolute maximum depending on which one used, probably less. my last calculations were: 93lc46: £0.26 93lc86: £0.62

i can confirm game crashes when pressing b on the high score entry screen

my switchblade arrived today. i am unsure why there has been some cost cutting here? it does not appear to be as good a quality a product as custodian was. the cartridge label is not big enough for the cartridge the cartridge label looks like it has been drawn on with a ball point pen down one side my manual appears to have been crumpled somehow the custodian label is not a correct jaguar cart label (rounded edges at the top and flat at the bottom) but it is much better than the switchblade label. and in my opinion acceptable as for the game, it works, i haven't tried it apart from making sure it boots, i will have a go later. i would think a good job was done with this considering who got it running the box looks OK, apart from the orange '64 - bit' which kind of sticks out. the jaguar standard is yellow is it not?, it was orange on custodian but it was a slight inconvenience, just thought i would mention it here because of the other bits

im sure making 1 extra board on this occasion wont kill me

what firmware do you need to play Boxxle on the ultimate sd? i just get a black screen using the following firmware Hardware 20141104 Boot 20150207 Menu 20141102 Firmware 20141102 i attempted to contact Steve and requested the latest firmware but he doesn't get back very fast or never gets back to you unfortunately

i have seen said boxes, however it isn't my place to share said boxes i just make the boards

http://atariage.com/forums/topic/268228-orion-re-releases-pre-orders-now-open/?p=3820811

http://atariage.com/forums/topic/243746-wip-kaboom/?p=3572312

unfortunately 'fools' will still buy this, some 'fools' will even think this is the best thing ever. if these people have no clue what they are buying let them buy this shit i certainly wont be, not only because this this is an absolutely terrible remake of a classic, but because its creator has previously attempted and was caught red handed selling my software i have gave away or free on ebay (which is why there have been no further versions of it released to the public)

if the two EPROMs have the same space on them and the same pins but in a different order the only problem you have is the chip pinout. rewire the pins as necessary. the host hardware will not know or care the chips are different because it will be wired the same as the original chip so to speak

the cartridge manufacture files are fine, there are many boards made to those specifications and they work, im not sure why you would want to change something that already works

if you want to make it the best compatability, on the eeprom save chip you need to connect the ORG pin to the +5V pin to set the save chip into 16 bit mode, this way 'new' revision eeproms will not need a bit or additional wire adding to make them work properly 93lc46C are chips that do not work without said bit of wire. once this is added they work fine

the lack of your reading ability you seem to have seems to add to your bug creation / non fixing issues, because you cant seem to read your code properly to to fix it, you even ignore information given to you by others so. you really should fix that issue of yours!

.

edge_wrap

edge_kill

why are you still using obsolete code? move over to RLIST rlist [plusrocka].active = R_is_active

i could also expect that this seller lacks the knowledge to actually make a working jaguar cd himself, so there is no doubt in my mind that the cd is also using others work made with jiffi. so in effect shitting on two active developers at once

While we are on the subject of Kizza, this was found some time ago. He has in fact a complete article on his antics. So he is well known in many areas / communities to be a lazy good for nothing lying scumbag check page 83 of this ZXShedIssue03.pdf

having trouble making cartridges of other peoples work to sell are we?? this is a good thing you know! if you did more reading rather than burning EPROMs you may know the answer by now

I have now finished the program to control this project (the ability exists to reprogram the controller so future updates can be done every jaguar joypad button does something the buttons directly mapping to the colecovision joypad perform the came function. the jaguar pad option button has three settings, set jaguar pad buttons c/b, b/a, c/a as colecovision left and right fire buttons jaguar pad button pause saves the current fire button configuration to the controllers internal eeprom, this is then reloaded when during the next power on, this way the user can set what is most comfortable for them i need to make a prototype on strip board and give it a good test before i do anything about making this a product / kit, hopefully there will be no or very few issues uncovered, power is still an issue but i have something coming that i am hoping will fix that how i want (steal power from the colecovision joypad port), that however is still WIP tests so far show this to be working correctly for those of you who like numbers: the controller program is 2.36k compiled the program uses 35 bytes controller ram the program uses 1 byte of eeprom space