Welshworrier

So the video from yesterday, which showed the coke can issue BTW, wasn't the version you are now saying Nick is producing for you (as you wouldn't have had the cart yet would you)... I'd also add that you've already shipped out a CD copy to someone on the jag fans fb group. They've received that and so have obtained a different version to the one you are now saying is fixed.

Since it doesn't display a version number it's an impossible question to answer.

Well since the collision detection faults were detailed last Saturday, the version 4 ROM came out Tuesday and the carts were shown yesterday. Either the cart production service is the quickest on the planet between countries (I'm assuming Nicolas is producing them), or something is not quite right about the timeline. The video that has since been deleted showed a cartridge taken from a box and exhibiting the usual faults. In any of the videos shown have a look at the red coke cans which seem to regularly pass through the mouth. Also worth mentioning that the eBay adverts don't actually show any pictures of it running - they are all box shots. He currently doesn't have any carts for sale though so maybe he pulled those. Edit: bah, took too long to type what CJ said

I received a PM from Jeffrey earlier today outlining some of the rationale behind the rush to market. I'll not make it public as he requested not to do so, however this is my abridged reply: Please understand I don't hate you - I don't actually know you. I do hate what you've done here, you've not taken any of the freely given advice and rushed to release with something that is going to hurt not just your own brand but will cause anyone else who's likely to be buying homebrew releases in the future to be suspect. Having the RB+ logo on there also will make it seem that the development suite isn't up to the job and so I can see Reboot. being less than impressed. From the questions you've asked it also shows that impatience to get something released for financial gain was the main driver - not actually wanting to give something to the 'community' or actually improve the product. The dogger to frogz 64 incident also showed the same - getting rid of the Jaguar system and CD that you mentioned in this thread would also mean that I can see that project never getting finished either - so what happens to those that paid for the Ebay demo copies who are expecting a full version? This game could have been good but will now be forever tainted. Would you buy a future product from someone who did that? Instead of addressing the problems mentioned here you are still promoting it on Ebay and the facebook groups - does that look like you regret your actions? While you may have issues it still doesn't give you the right to, in effect, rip people off by having them pay for a product you know has problems - how do you know that they don't have concerns that you've now made worse? Selling pirate roms has also damaged your relationship with developers - why would they now trust you with software if they know it had a chance of being sold for profit? It's a complete cluster brought on by your own behaviours.

So version 3 had "Reset to menu from PLUS mode fixed! Some VR and 2600 mode bugs fixed much more stable return to menu functions" And version 4 gave speed fixes. The word "some" in vr and 2600 mode fixes would indicate that some other bugs are not fixed. More stable return to menu also implies it's not 100% stable. I've got to ask "why the rush to get a cartridge out instead of waiting until it's working fully"?

I take it you are still going ahead with selling cartridges with the buggy version on it then. http://www.ebay.com/itm/222545167873

That's the PC version though

And thundercats is pretty awful, remember talking to programmer about it and he said it was too difficult to play but Elite insisted he shouldn't alter the difficulty.

Also a suggestion: start the animation cycles at different points so that they don't all look identical as they move left to right.

I reckon you'll look at the collection, know that people will have them in alphabetical order, and so will do games to make them have to split a letter over two shelves.

You should also add a flick option to see if you can get one ant to smash into another.

There are several errors I can see straight off, and I'd suggest you might want to invest some time in learning how to do debugging. 1. RSETOBJ(burger, R_sprite_scale_x, (burger, R_sprite_scale_x+1)) - now as the third parameter you are trying to pass has to be in the range 0 - 255, what do you actually think the (burger, R_sprite_scale_x+1) will give you? [hint: it isn't the current value plus 1] 2. RSETOBJ(burger, R_sprite_scale_y, (burger, R_sprite_scale_x+1<<16)) - much like #1 but this time even worse. You have tried shifting the old value, which you are not going to be getting anyways, left by 16 bits. It fails at that too as you have not followed the rules of operator precedence so a shift/multiply/divide would be carried out before addition i.e. you've tried adding 1 shifted left 16 times to it. i.e. 0. If it has the same result as attempt #1 it means you are using the wrong value. 3. sub scaleburger IF zoomtimer=0 THEN RSETOBJ(burger, R_sprite_scale_x, 16) RSETOBJ(burger, R_sprite_scale_y, 16) ENDIF IF zoomtimer=2 THEN etc..... Apart from being bad coding practise (as all IF statements will be calculated even if you match at the first one), the fact it sets the first size correctly means that zoomtimer is set to 0 at some point but not being incremented between calls to the subroutine. I take it you've actually checked the value when the subroutine is called. i.e. you are almost certainly re-initialising the variable inside the main loop. The code option shown by atari2600land is much better but needs checking for max scale AND should only rsetobj the scale values inside the if statement - i.e. when the scaling changes. (it also does it every 4th frame instead of 2 in your version)

I'd guessed just you were storing using the Union version but were reading using the full without the shift. I.e. rlist[ABC].x_ instead of rlist[ABC].x

Wouldn't the last x and y from there be the x_ and y_ versions (I take it they are overlays of the x and y integers)

You are just an old Ham at heart...

The kick starter idea would just be egging you on anyway (badum tish)

Take it the egg theme recently is due to Easter

I do wonder if the companion product to the Vid you posted would be appropriate https://youtu.be/LqL4DRZ2EkA

Ballpark figure seems to be about 100 to 120 quid for a boxed one with one controller. Games vary between 15 and about 45 for okay to good titles. If you check out Amazon you'll get a better idea.

If you check his profile he last appeared here in February of this year - maybe he'll update some time.

*requires time machine attachment to purchase

Gaz = slang for Gary and Tee = first letter of his surname at a guess.

ISTR the reason AA started doing the ST ROMs was because a few of the games started appearing on eBay at a premium price.

I sometimes get the feeling it's only the speed of Australian broadband to upload the videos that is hindering the games completions

The sound chips are different between the ST and the jag. This means all the ST sound routines need to be rewritten from scratch or replaced with sampled versions for the conversions. Native is a different case as that's a jag native game that is maxing out the display processing side and they never added sound - which would have impacted the graphics.