Reshoot R crashing!

[Patrickx1989]

Thanks for the reply, Richard. I honestly don't know where the problem exactly lies, but I must admit that I am still quite new to emulation. Even if I set the chip memory to 8MB under the WinUAE "RAM" setting, it still - as soon as I am in Workbench - only has a little bit over 1MB free Chipmem. It doesn't seem to make any difference what I set the Chipmemory in the emulator to

Edit: I also use a preinstalled package called AmigaSYS and it just loads Workbench, I don't really know how to change it? How can "switch off" tools?

I don't want to be too critical, and I appreciate your willingness to support, but still, I am wondering why this is the only game causing such issues? Other similar ones (such as Crossfire, Wendetta or T-Zero) work fine because they apparently use other types of memory. I am reminded of my early DOS years on PC when I struggled to free up conventional memory..... And sorry, but this is not about "so many AMIGA configurations": Multiple users in various forums have reported similar problems, both on emulators and on "real" AMIGAs. The problem is the too-high Chip-mem requirement.

[buzzybee]

Originally Posted by Patrickx1989

Thanks for the reply, Richard. I honestly don't know where the problem exactly lies, but I must admit that I am still quite new to emulation. Even if I set the chip memory to 8MB under the WinUAE "RAM" setting, it still - as soon as I am in Workbench - only has a little bit over 1MB free Chipmem. It doesn't seem to make any difference what I set the Chipmemory in the emulator to

Edit: I also use a preinstalled package called AmigaSYS and it just loads Workbench, I don't really know how to change it? How can "switch off" tools?

I don't want to be too critical, and I appreciate your willingness to support, but still, I am wondering why this is the only game causing such issues? Other similar ones (such as Crossfire, Wendetta or T-Zero) work fine because they apparently use other types of memory. I am reminded of my early DOS years on PC when I struggled to free up conventional memory..... And sorry, but this is not about "so many AMIGA configurations": Multiple users in various forums have reported similar problems, both on emulators and on "real" AMIGAs. The problem is the too-high Chip-mem requirement.

Who was first, the hen or the egg? Does RR use too much chipmem and should better only use 1 MB? Or does it make sense to use 2 MB of Chipmem, to achieve max visual effects?

Anyway, your problem is obviously a serious lack of chipmem. Only having 1 MB of Chipmem available on WB, while you set the emulation to 8 MB, could mean you are running a ton of resident tools and/or there is a serious problem with your emulation setup. Sorry, as I do not the WB package you are using, I cannot assist you in this special case. Maybe open up another thread and ask Emulation-specialist for assistance? EAB is the right place for this.

If I were you, I'd just setup a second Amiga-emulation, with a naked A1200 and 2 MB Fastmem. Game will run perfectly.

[malko]

Originally Posted by Patrickx1989

[..] Even if I set the chip memory to 8MB under the WinUAE "RAM" setting, it still - as soon as I am in Workbench - only has a little bit over 1MB free Chipmem. [...] I am wondering why this is the only game causing such issues? Other similar ones (such as Crossfire, Wendetta or T-Zero) work fine [...] The problem is the too-high Chip-mem requirement.

My two cents. Reshoot-R system requirements :

System requirements
Amiga 1200, Amiga 4000 oder CD32
Joystick or CD32-compatible controller
2 MB Fast-RAM or more recommend
Also runs on compatible Amiga-emulator (Windows, Mac, Linux and more)

source: https://reshootr.richard-loewenstein.de/


If you really have 7MB of ChipMem eaten by other applications () , I would see it more appropriate to re-think the question the inverted way : "What are those applications that 'eat' 7MB of ChipMem. Are they worth it ?
Can I get rid of some of them to have a better WB experience ?

Originally Posted by Patrickx1989

[..] I am reminded of my early DOS years on PC when I struggled to free up conventional memory..... [..]

You cannot compared the hassle a config.sys & autoexec.bat, huumm, "tuning" used to be with how things are handled on an Amiga, but yes, you can also 'script' a bit your 'startup-sequence' to handle a boot that will load nothing BUT the game (maybe check your WBStartup folder as well if you have one).
If you miss knowledge to do so, the following link can be a starter : https://wiki.amigaos.net/wiki/AmigaO..._Using_Scripts

[DamienD]

@Patrickx1989; I'm sure in my collection I've setup a bare-bones / self-booting .HDF for Reshoot R with trainer added

As you've purchased this game, I could send you this.

Then you just use a standard "AGA - 2MB Chip" configuration and just point to the .HDF

[Patrickx1989]

Thanks a lot, DamienD, but I managed to get it to work by really making a new A1200 config and installing WB 3.1 from the disk images with just the minimum stuff (meaning just grey colors etc.) It was a bit of a hassle, but at least I learnt something more about Amiga emulation, so I guess it was worth the time
Overally, a great game, although I do hope Reshoot proxima 3 (which I most certainly will buy too) finds a more "forgiving" solution to the memory usage.

[DamienD]

Alrighty

...and good to learn new things related to the Amiga.

[snowpile79]

I just purchased Reshoot R and was having similar issues. Wanted to post in order to help others play this on real hardware similar to mine. I have an Amiga 4000 with KS 3.1.4, 040 25mhz, 272meg ram, MNT va2000 graphics card, Xsurf 100, rapid Road USB, Buddah Flash 20th Anniversary, CD-RW.
Possibly special items at play: MuLibs (but as you can see form my attempts below this was eliminated as an issue when I booted off 3.1.4 workbench floppy).
First what I tried.
1) Running the game outright. Nope. Flips to gray screen, reads CDrom for 4 sec. Freezes sometimes reboots the rig.
2) Installed on the HD. Nope same issue.
3) Slowly commented out all startup-sequence and user-startup. Nope same issues (running off HD)
4) Booted off 3.1.4 Workbench disk. Ran game off HD with 1.90meg chip ram free. Nope
5) Flipped my PAL/NTSC switch to PAL, Boot off floppy. Nope
6) Boot off HD again but with no startup-sequence (just boot to CLI). Ran by hand in PAL mode.
7) Switched gears. Made a CD-32 emulator boot disk using IDE-FIX 97. Booted and ran the CD every which way with all the checkboxes checked or unchecked. Every combo. Nope.
8) When the WHDLoad route. Downloaded the ReShoot R whdload install and ran the install against the CD. Fired it up!!!! Nope.. LOL.
9) Started Mucking about with the WHDLoad parameters. Tried PAL mode. SUCCESS!!! Works perfectly in WHDload. If you read the readme about the slave in the change history it says they fix something specific to the Amiga 4000. I forgot what it was now but I think this just simply doesnt run on an A4000 OR you must have KS 3.1 or below but the WHDload slave readme seems to say they disable some type of graphics switching that the A4000 doesnt like??

Anyways WHDLoad works like a charm in PAL mode. This should also allow the game to run on any A1200/A4000 upgraded or not no matter what CPU etc.. It ran at the normal speed even with my 040 and no special tweaks like shutting off cache.

[buzzybee]

Originally Posted by snowpile79

I just purchased Reshoot R and was having similar issues. Wanted to post in order to help others play this on real hardware similar to mine. I have an Amiga 4000 with KS 3.1.4, 040 25mhz, 272meg ram, MNT va2000 graphics card, Xsurf 100, rapid Road USB, Buddah Flash 20th Anniversary, CD-RW.
Possibly special items at play: MuLibs (but as you can see form my attempts below this was eliminated as an issue when I booted off 3.1.4 workbench floppy).
First what I tried.
1) Running the game outright. Nope. Flips to gray screen, reads CDrom for 4 sec. Freezes sometimes reboots the rig.
2) Installed on the HD. Nope same issue.
3) Slowly commented out all startup-sequence and user-startup. Nope same issues (running off HD)
4) Booted off 3.1.4 Workbench disk. Ran game off HD with 1.90meg chip ram free. Nope
5) Flipped my PAL/NTSC switch to PAL, Boot off floppy. Nope
6) Boot off HD again but with no startup-sequence (just boot to CLI). Ran by hand in PAL mode.
7) Switched gears. Made a CD-32 emulator boot disk using IDE-FIX 97. Booted and ran the CD every which way with all the checkboxes checked or unchecked. Every combo. Nope.
8) When the WHDLoad route. Downloaded the ReShoot R whdload install and ran the install against the CD. Fired it up!!!! Nope.. LOL.
9) Started Mucking about with the WHDLoad parameters. Tried PAL mode. SUCCESS!!! Works perfectly in WHDload. If you read the readme about the slave in the change history it says they fix something specific to the Amiga 4000. I forgot what it was now but I think this just simply doesnt run on an A4000 OR you must have KS 3.1 or below but the WHDload slave readme seems to say they disable some type of graphics switching that the A4000 doesnt like??

Anyways WHDLoad works like a charm in PAL mode. This should also allow the game to run on any A1200/A4000 upgraded or not no matter what CPU etc.. It ran at the normal speed even with my 040 and no special tweaks like shutting off cache.

Thanks for the detailed description of what you did to make my game run on your config. This will certainly help others if they run into trouble running RESHOOT R.

Regarding 9), just if you want to know: WHDLoad contains a fix that disables code that sets a bit only needed when the game is run on CD32. I implemented this code very late in the dev process, in fact, it is not contained on the very first batch of CD-ROMs which got delivered to some people. Unfortunately, this code breaks the game on some A4000 as on these machines, it disables ROM (whereas on CD32, it prevents the console from playing broken CD-Audio-sound). This does not happen on any other Amiga-machine, also not on emulated A4000, only on some real A4000.

The game generally disables all caches it does not need, regardless of the CPU. It also syncs to Vertical Blank and therefore should always run at the desired speed, regardless of the speed of the CPU.

Anyway, thanks for your patience. I am so happy that you can now enjoy the game. Have fun!

[legolas119]

hi, i tried several times but i'm not able to run the game. Please, can anyone help me showing the FS-UAE settings in order to run it?
thank you very much!