Tinyus Open Beta Released (OCS Gradius port)

[DanyPPC]

Tinyus recently had a new slave:

http://www.whdload.de/games/Tinyus.html

[hexaae]

Originally Posted by DanyPPC

Tinyus recently had a new slave:

http://www.whdload.de/games/Tinyus.html

That's the one I used for testing and 1st boss fight is buggy. With generic Kick3.1 slave in the Zone is fine.

[DanyPPC]

Ok, thanks.

[Torti-the-Smurf]

Just asking; but why even using a WHDLoad Slave for this Game ?

Is there some exotic Setup where it goes nutz ?

; worked flawless on everything i have tried and you can exit at any point with ESC.

Mr. Pink Quality

I am asking out of curiosity

Greetings,
Torti

[nikosidis]

Originally Posted by Torti-the-Smurf

Just asking; but why even using a WHDLoad Slave for this Game ?

Is there some exotic Setup where it goes nutz ?

; worked flawless on everything i have tried and you can exit at any point with ESC.

Mr. Pink Quality

I am asking out of curiosity

Greetings,
Torti

Haha, yes, I wonder too


It is simply no reason for whd-load

[jotd]

That one is actually a good match.

I was asked some months ago (by a guy named Steve) if I could create a CD32 bootable version of that game. With the executable, it just doesn't start. I think that's a cranker/modern decruncher issue.

Just that part prevents from burning the exe and starting it from CD32.

With the generic slave (or the unoffical one that I created and forgot to publish at the time) it worked, but required kickstart so I couldn't create an ISO for copyright reasons. That slave (even if there are issues) is able to get around those issues.

Plus the possible conflicts that whdload usually resolves: display, getting mouse pointer in the proper resolution when quitting, not corrupting OS memory, turning off network cards, etc... Small things. No matter how good your startup / cleanup procedure is and your game coding, there's always something that whdload does and your code does not.

[mahen]

I noticed that the volcanoes do not erupt before the boss appears with the WHDLOAD version. (it's not just that the level doesn't end but a whole "scene" is not triggered) Cheers

[Torti-the-Smurf]

Originally Posted by jotd

No matter how good your startup / cleanup procedure is and your game coding, there's always something that whdload does and your code does not.

Introduce new Bugs ?

( please, don´t hit me JOTD ; just kidding )

I freaking love and adore your work;
and all the creators of the WHDLoad Slaves shall be praised !
Letlone WEPL who created WHDLoad !!

One of the best & most essential Amiga Software ever written !!! (JST rocks too !!!)

I get what you are saying JOTD; i really do;

but in "some" cases WHDLoad makes no sense.

(Before you go into berserk mode ; PLEASE let me explain, ok ? )

I give a simple and classic Example, ok ?

Lets say... The Secret of Monkey Island (and yes; i have the Code Wheel !!)

1) Let´s take a real OCS/ECS Amiga with a CF/Harddisk;
Why should i wait for the preload + OS Flashes (if the Ram is not enough); maybe even risk possible crashes, when the game has a native install and runs like a dream on that Setup. ?

2) On an AGA Amiga the game has a stupid graphic glitch and going into
the early Startup-Menu to change the Chip to OCS/ECS is;well, kinda annoying.

There i use the WHDLoad version for sure !!!

(Thank you so very much for that slave JOTD & ALL the other Slaves you did )
---------------------------------------------------------------------
So; i find it depends on the circumstances. (imho)

There are OCS games however,that have problems with some OCS machines, because of a CPU upgrade or Fast-Ram which can confuse the game/was not programmed to handle.

There is where the strengh of WHDLoad really lies ( at least imo )

WHDLoad solves so many problems BUT it can also introduce some

Originally Posted by torturedutopian

I noticed that the volcanoes do not erupt before the boss appears with the WHDLOAD version. (it's not just that the level doesn't end but a whole "scene" is not triggered) Cheers

I depends on the case (like the one in my example above)

Yes, i mostly use WHDLoad slaves, but there are a few cases where i simply dont need it

Just my take Please dont get mad at me JOTD; i adore your stuff Man

[jotd]

Why should I be mad? your examples make sense and you are entitled to your opinions and yes whdload is less useful for some games than for some others. The pink^abyss startup code is very good (one of the best around) so why bother with whdload if you don't need it.

Personally I like simple launcher scripts. If all scripts use whdload I don't have to configure them further for them to run. whdload contains all data, assigns, required memory, quitkey...

Just an uniform way to run stuff.

Plus there's always the ability to fix small bugs / add trainers without begging the original team to change the game again and again. Yes sometimes the whdload layer introduces bugs. For instance if not enough memory is allocated to the game, strange things can occur.

for instance in Wrong Way Driver I have noticed that on fast machines (winuae) the opponent cars & bonuses are not properly drawn. This is very probably a blitter issue that I'm trying to fix using whdload. Does that require a new release of the game? maybe not.

have fun!

[hexaae]

Originally Posted by Torti-the-Smurf

Just asking; but why even using a WHDLoad Slave for this Game ?

Is there some exotic Setup where it goes nutz ?

; worked flawless on everything i have tried and you can exit at any point with ESC.

Mr. Pink Quality

I am asking out of curiosity

Greetings,
Torti

Yes. Try for example to launch games like Barbarian+ after it... I suppose some (audio) registers are not cleaned up on exit. Generic WHDLoad launch protection solves any issue.

[Torti-the-Smurf]

@ JOTD : i like Cats & i like You

@ hexaae : I was asking specifically about TinyUS in that post !

Anyway; enjoy your Time with Amiga & have Fun

Yours truly,
Torti

[hexaae]

Originally Posted by Torti-the-Smurf

@ hexaae : I was asking specifically about TinyUS in that post !

Well, if a game running and quitting to/from WB is unstable and/or can cause issues with other programs after you run it, this is a good reason to use WHLoad even though the game itself runs fine from WB. If you use your Amiga as a console through disk loading and reboot when finished of course is never a problem, but when you have a Workbench environment it's annoying.

[Torti-the-Smurf]

Sure; 100% agree.
I use WHDLoad on a daily basis too

[ImmortalA1000]

Any progress on getting a CDTV bootable or non booting ISO (via Workbench floppy connected to my CDTV?) etc?

Don't want to play it on an LCD using my crappy PC keyboard, waste of time, and the Gotek is a bit fracked for some reason and it will be a long time before I have spare cash to buy another.