Overview Features Instructions Performance Forum Downloads Products OrderV4 Reseller Contact

Welcome to the Apollo Forum

This forum is for people interested in the APOLLO CPU.
Please read the forum usage manual.



All TopicsNewsPerformanceGamesDemosApolloVampireAROSWorkbenchATARIReleases
Running Games and Apps.

WHDLoad Issues - Some Games Too Fast

Bart Mikulski

Posts 100
20 Mar 2018 12:38


Hi!
 
My setup - Vampire 600 v2 + Coffin R49, Gold 2.8.
 
  Some WHDLoad games (Baby Jo Going Home, MYTH, DanDare) run to fast.
 
  I tried messing about with all the possible WHDLoad tooltypes (nocache, expchip and many more) as well as the core itself (turtle mode) - to no avail.
 
  Is there any solution to this? Thanks!


Vojin Vidanovic

Posts 1697
20 Mar 2018 13:49


Bart Mikulski wrote:
 
      I tried messing about with all the possible WHDLoad tooltypes (nocache, expchip and many more) as well as the core itself (turtle mode) - to no avail.
   

   
    Thanks for sharing the problem.
   
    As always, core revisions can introduce small troubles to be fixed, even Coffin included software was 2.7 tested.
   
    Sometimes tring beta or older WHDLoad helps (e.g. current beta is 1.84 EXTERNAL LINK )
   
    Also some problems are slave specific.
   
    As Example, if its this Myth slave file EXTERNAL LINK it has some extra requirements in notes.
 
  If its System 3 myth, this should be the latest slave EXTERNAL LINK
   
    As always with WHDLoad, reading of general instructions helps :-) As well as bug reporting to WHDLoad team, too.
 
 
  From the WHDLoad page
 
  ------------------------------------
    If the install does not work?
  ------------------------------------
 
    First, don't panic, don't swear at the install, don't swear at WHDLoad and don't flame at forums or comp.sys.*.*. It's usually the fault of the games or demos if they do not work and the install tries their best to make them working on all hardware setups.
   
    In fact all installs are written to work with an ORIGINAL, that means that the install will usually not work with versions which has been altered in any way.
   
    Before sending a bug report, try yourself to solve the problem. There are various things you can do:
   
        check the version of the install and WHDLoad, make sure that you are using the latest versions of both, many installs require the latest WHDLoad version, also installs will be updated from time to time - so check if there is an new one available
        check the Tooltypes (or the options if started from the CLI/Shell), many things can be adjusted setting Tooltypes, there is hardware which requires that you set the correct Tooltypes, maybe your system is to fast - so set NoCache, some games are working only under PAL or NTSC - so try the Tooltypes PAL and NTSC, some extra hardware creates at random interrupts which confuses the installed games/demo - so try Tooltype NoAutoVec, sometimes also the Tooltypes NoResInt and NoMMU may help
        read the readme or other documentation supplied with the install, it often contains important information concerning the install, its using and its limitations
   
    Although all installs are tested before public release, a bug might have escaped unnoticed. If you think you discovered a bug, write a detailed report of your problem to the author of the install. For this use the bug report form which can be accessed if you click on the author on the download pages. Or submit a report in the Mantis Bugtracker. Try to report your problem accurate. If you get an error requester by WHDLoad please also make a CoreDump (just press the CoreDump button on the requester WHDLoad shows) and attach the .whdl_register file to the issue made in the Mantis Bugtracker. Problems reported via the form on the download pages will be imported some days later to the Mantis Bugtracker. During that process an user account for the reporter will be created (if not already present). All further communication regarding the report should then happen via the bug tracker so that the relevant informations can be preserved.
   
    Please note: if the authors aren't informed about bugs they can't correct them.
   
    Note also, that the reasons for problems are often an different version of the game/demo. Many commercial games have been sold in more than one version (full-price-release, budget-re-release, coverdisk-release, PAL/NTSC version, ...). Of course a install can only work if it has been written for the version you have. If you have a different version of the same game, it won't work. In that case, you have to contact the author of the install and ask him to support your version.


Michael AMike

Posts 130
20 Mar 2018 14:33


Have you tried the turtle mode? Open shell and type: vcontrol turtle=1


Bart Mikulski

Posts 100
20 Mar 2018 16:40


Michael AMike wrote:

Have you tried the turtle mode? Open shell and type: vcontrol turtle=1

Yes, I have - doesn't solve the issues.


Gunnar von Boehn
(Apollo Team Member)
Posts 4795
20 Mar 2018 18:47


Bart Mikulski wrote:

Michael AMike wrote:

  Have you tried the turtle mode? Open shell and type: vcontrol turtle=1
 

 
  Yes, I have - doesn't solve the issues.

Setting Turtle mode will work if you launch a normal application.
if you use WHDLOAD this will NOT work as WHDLOAD will overwrite this setting on its own on launch!

NOCACHE Setting in WHDLOAD should work


Matthew Burroughs

Posts 59
20 Mar 2018 19:25


WOW

SIMPLY WOW

Old Amiga games running too fast on new Amiga hardware.

Never thought we would ever have this problem.

The child in me is happy, very happy.


Bart Mikulski

Posts 100
20 Mar 2018 19:35


Thank you for the tips, everyone!

Gunnar von Boehn wrote:

Bart Mikulski wrote:

 
Michael AMike wrote:

  Have you tried the turtle mode? Open shell and type: vcontrol turtle=1
 

 
  Yes, I have - doesn't solve the issues.
 

  Setting Turtle mode will work if you launch a normal application.
  if you use WHDLOAD this will NOT work as WHDLOAD will overwrite this setting on its own on launch!
 
 
  NOCACHE Setting in WHDLOAD should work

With NOCACHE - Baby Joe won't start at all (I see "writing to disk" window, then nothing), MYTH - still runs too fast.

posts 7