Rayman 3: Hoodlum Havoc

Retail release

Application Details:

Version: 1.0.0
Votes: 0
Latest Rating: Silver
Latest Wine Version Tested: 3.0.3

Maintainers: About Maintainership

No maintainers. Volunteer today!

Test Results

Old test results
The test results you have selected are very old and may not represent the current state of Wine.
Selected Test Results

What works

Note: Rayman3 installer will end as soon as it tries to switch to CD 2, follow the installation instruction to workaround.

Everything in the game worked, opening screen, cinematic, gameplay, changing sound/control settings, saving options, game's automatic save, in-game screenshot capturing, albums, bonus items, 3D settings.
Graphics was good and sound was OK. Joystick control also fully worked too!

Using Alt+Tab for switching in/out the game and Alt+F4 to exit also usable.

Installation Instruction (The Easy Way)
For ones who didn't hesitate to use winetricks or native dll.

  1. Install native MSI by using one of the method provided at[1]
  2. Set WINE Windows version 98. [2]
  3. Run winefile from your home directory.
  4. Go to your CD drive in winefile.
  5. Run setup.exe, and quit winefile. [3]
  6. Follow the installation as normal, but don't install directX, and registration won't work. (Installer will prompt you to change disc as normal, if you can't eject, fire up a terminal, and use "wine eject" command)
  7. Set WINE Windows version XP. [4]
  8. Then, run it as normal (insert CD2/3, and run Rayman3 from start menu or program files).
Installation Instruction (The Hard Way, for full installation only)
For ones who didn't want native dll and/or want to report a bug, since it was discouraged to submit bug report with native dll.
This needs additional ~1.7GB disk space for temporary files.
  1. Copy all files from three CD into one directory (with overwriting).
    Each time you finished copying a single CD, you need to sort out permission problem by using a command "chmod -R +w your_copying_destination" before you start copying the next disc.
  2. Run setup.exe from that directory.
  3. Follow the installation as normal, but don't install directX, and registration won't work. (Installer will not prompt for disc change too)
  4. When the installation finished, the copied files had no use anymore, you may delete them.
  5. Then, run it as normal (insert CD2/3, and run Rayman3 from start menu or program files).

[1] To avoid WINE's MSI bug that caused Rayman3 installer not to prompt for disk change.
[2] To avoid "The Windows Installer Service could not be accessed" or "Unable to install InstallShield Scripting Runtime.", since Windows 98 is not using service for windows installer.
[3] To avoid situation that you cannot eject disc.
[4] To avoid "debugger has been detected" issue.

What does not

  • Registration, when running register.exe it just shown an error "Run-time error '429': ActiveX component can't create object", and terminated.
  • Minimal installation with WINE's MSI, it gives no difference to full installation (both occupy 1.7GB disk space).
  • Uninstallation with WINE's MSI, it did nothing apart from making Rayman3 entry in Add/Remove program unusable, the game was still playable, saved game was still there.
    (Uninstallation with native MSI was OK, you also need to set WINE to Windows 98 before uninstalling too)


What was not tested

  • Playing through the end of The Clearleaf Forest, and later level
  • Lums Race

Hardware tested


  • GPU:
  • Driver:

Additional Comments

- It seems that even 'full installation' specifically needs CD2 to be inserted when loading an early level (eg. The Fairy Council), don't know if it was a bug or not. - Beware when disc was inserted during game, file manager would pops up (but may not visible), making the game pause, use Alt+Tab to switch back to the game. I suspected that game's sound mixing quality wasn't good as on Windows, don't know if it was a bug in WINE, or a bug in my ear. If you run Rayman3 from command line and noticed performace degrade or out-of-sync in cinematic, that might be due to a lot of FIXMEs wine printed on the console. Running Rayman3 with FIXMEs trace disabled (using "WINEDEBUG=fixme-all wine rayman3.exe") should help. For ones who didn't use command line, this shouldn't be a problem. Tested with WINE's Windows version XP (setting to 95/98/ME the game will complain "A debugger has been detected: Unload the debugger and try again") Graphics: ATI Radeon HD 4670 with fglrx driver Audio: Intel HDA (Realtek ALC880) WINE audio settings: ALSA, 44100Hz, 16bit, Full hardware acceleration

selected in Test Results table below
Operating systemTest dateWine versionInstalls?Runs?Used
ShowUbuntu 16.04 "Xenial" amd64 (+ variants like Kubuntu)Nov 01 20183.0.3Yes Yes YesSilverTaamer 
ShowUbuntu 12.04 "Precise" i386 (+ variants like Kubuntu)Jun 24 20141.7.19Yes Yes Garbagean anonymous user 
ShowGentoo Linux x86_64Nov 11 20131.6Yes Yes SilverIgor 
ShowUbuntu 12.04 "Precise" i386 (+ variants like Kubuntu)Jul 23 20131.6Yes Yes Bronzean anonymous user 
ShowArch Linux x86_64May 19 20121.5.4Yes Yes BronzeAustin 

Known Bugs

Bug # Description Status Resolution Other apps affected

Show all bugs


Comments Disabled

Comments for this application have been disabled because there are no maintainers.