Warhead audio (from preinstalled)

[NewDeli]

Hi,


Sorry, I couldn't load properly any ADFs (nor the IPF) due to some warning about strange bootloaders, so I can only confirm this from the preinstalled version of Warhead.

Audio from the intro would be (almost) completely garbled.
The bug doesn't occur on an actual A1200.
I hope it's not my A4000 config. settings again .

[Toni Wilen]

Warhead audio routines are really bad (programmer clearly didn't know how to program Amiga audio hardware...)

Requires something cycle-exact like chip ram accesses to work.

(this was an expection, normally I won't care about whdload problems)

[dlfrsilver]

@Deleauvive :

Once again i told you yesterday that i had perfect sound on Warhead with cycle exact.

Why are you posting this ? what's the point of me testing the fucking game for you if after you come here to say there is a problem when I TOLD WHAT YOU NEED TO DO TO GET THE SOUND RIGHT ?

I said with CYCLE EXACT IT WORKS !

[NewDeli]

Why are you taking this personally ?
I thought you had this game tested with your Amiga.
I submitted many games for you to test so I might have forgotten about this one in particular.
The audio fails for me even with cycle-exact.

What's wrong with asking again for advice anyway ?
It's not even a case of me bothering whdload coders about this issue .

[dlfrsilver]

you told me the game had problems with audio. I have tested on my A1200 + winuae with my settings FOR YOU

Remember ? No JIT + Cycle exact >:/

[NewDeli]

we don't have the same PC (mine is not a Quad core) nor the exact same settings, at least Host side.

I use cycle-exact for all my games, ADFs, preinstalled whatever since beta 15.
JIT is not activated either, and I made a thread to mention where I mention that at least two games would require cycle-exact enabled. Also, I am mostly grateful for the support you offer for slaves presumably buggy (but in the end were not).

I think I have made sufficient statements about the importance of using this feature, so I suggest you redirect your advice to the Whine UAE users that still aren't aware of this.



May I remind you that Toni mentioned it's incomplete, and not even suited for 030 or 040, so how would we convince people to accept the idea of loading their ClassicWB, AmigaSYS or similar preconfigured WB since 020 is not the recommended CPU type to run these ?

...taken from AmigaSYS 4.uae

cpu_type=68040
cpu_model=68040
fpu_model=68040

[TCD]

Originally Posted by Deleauvive

Sorry, I couldn't load properly any ADFs (nor the IPF) due to some warning about strange bootloaders, so I can only confirm this from the preinstalled version of Warhead.

Hmm, 'Warhead (1990)(MPH)[cr ACC]' works a treat with the (you knew it was coming ) A500 most common quickstart (latest beta). Audio is fine of course. Wonder how you managed to get that warning...

[NewDeli]

Originally Posted by Deleauvive

I didn't want to load any ADFs (nor the IPF) due to some warning about strange bootloaders.

Here it what Virus Checker II displays about it :

You're right. I can hear the spooky music loud and clear from that ADF. Now the question remains whether it could be worth the effort to fix the audio when the game is started in its preinstalled version, NOT from a real machine (and NOT from dlfrsilver PC ).

[TCD]

'NON-STANDARD BootCode'... The disks boots? You could test it? Why your message in the first post about 'couldn't load properly any ADFs'

[NewDeli]

The disk boots indeed, it's the same copy as yours.

What I really meant was "couldn't load properly from the WB, because of the requester." Anyway, the file is not marked as virus'd in the TOSEC naming convention, so I guess I can boot it safely.

You're not telling me if the audio from intro works with the preinstalled version on your PC, that's the part I mostly wish to know about .

[TCD]

Originally Posted by Deleauvive

What I really meant was "couldn't load properly from the WB, because of the requester." Anyway, the file is not marked as virus'd in the TOSEC naming convention, so I guess I can boot it safely.

That message just means that it's not an ADos disk. Always boot from an ADF if there isn't a reason (HD installer) not to do it.

Originally Posted by Deleauvive

You're not telling me if the audio from intro works with the preinstalled version on your PC, that's the part I mostly wish to know about .

Works flawlessly with cycle exact here aswell. If I turn cycle exact off I can hear what you mean.

[dlfrsilver]

Originally Posted by Deleauvive

Here it what Virus Checker II displays about it :

You're right. I can hear the spooky music loud and clear from that ADF. Now the question remains whether it could be worth the effort to fix the audio when the game is started in its preinstalled version, NOT from a real machine (and NOT from dlfrsilver PC ).

The disk boots indeed, it's the same copy as yours.

What I really meant was "couldn't load properly from the WB, because of the requester." Anyway, the file is not marked as virus'd in the TOSEC naming convention, so I guess I can boot it safely.

You're not telling me if the audio from intro works with the preinstalled version on your PC, that's the part I mostly wish to know about .

1) What Virus checker II tells you is that this game is NON-DOS. It uses a custom bootstrap. This is not a virus or whatever. And it has nothing to do with Pre-installed version anyway.

2) You said : "Now the question remains whether it could be worth the effort to fix the audio when the game is started in its preinstalled version, NOT from a real machine (and NOT from dlfrsilver PC )."

There is no POINT for a slave coder to correct something that is due to unwanted settings. Those you are using for pre-installed versions. About what Toni said, even if the coder didn't know a thing about coding the amiga audio hardware, IT WORKS on a real A1200 (mine), it WORKS on my winuae config on my PC.

So the answer to your question about fixing it is no. If they did (and i don't think this will happens sooner or later) it would then come again on debate fixing games for winuae that work correctly with a real machine.

[TCD]

Originally Posted by dlfrsilver

IT WORKS on a real A1200 (mine), it WORKS on my winuae config on my PC.

On mine aswell. I bet if some other folks would test it we could get a clearer picture if it has anything to do with the host PC. I would say it doesn't matter.

[NewDeli]

With all due respect, I think this issue is beyond the scope of JIT/noJIT, Cycle exact / no cycle-exact, at least on WinUAE.

See, when I set the chipset to full ECS instead of AGA, problem is gone.

I trust uae-configuration sitting in my path to enable/disable the settings I set in whdload.prefs right when the game starts, btw.

ExecuteStartup=uae-configuration cachesize 0 cpu_cycle_exact true

[TCD]

Originally Posted by Deleauvive

With all due respect, I think this issue is beyond the scope of JIT/noJIT, Cycle exact / no cycle-exact, at least on WinUAE.

It works on a real A1200, it works on WinUAE with the 'right' settings = nothing to care about for WHDLoad.

[dlfrsilver]

in fact, the PC type (dual-core or quadricore) has NOTHING to do here with what Warhead needs. Maybe winuae will run faster on slow PC without some settings in particular cycle exact or JIT), but if those create some bugs then the user must not complain.

You use the settings the game need to run under winuae, or you buy a new PC to get the processing power required.

If i ask myself Toni 'hey Toni, game has bugs because i can't use the settings for this same game' for sure he will answer me 'go buy a new machine'.

Don't you agree ?

[NewDeli]

Originally Posted by TheCyberDruid

nothing to care about for WHDLoad.

Well, I was not planning to make a bug report, simply write an informal email to wepl about it. Don't mind if I do ?

[dlfrsilver]

it will be useless. Stop that !

also :

you wrote : "I trust uae-configuration sitting in my path to enable/disable the settings I set in whdload.prefs right when the game starts, btw."

uae-configuration has NOTHING to do with whdload.prefs. Nothing !

[TCD]

Originally Posted by Deleauvive

Don't mind if I do ?

Actually I kinda do. Why write about it if there's nothing more than a config issue in WinUAE? There is no problem with the slave. It would be a wasted efford to make it work with all WHDLoad capable real Amigas and WinUAE configs. Since you can easily make it work in WinUAE (now), why bother to 'fix' something that isn't really broken?

[dlfrsilver]

well maybe my voice and TCD's will make you hear it right this time.

"If it ain't broken, don't fix it". American saying