Fade

Contents 1 Descrition: 2 Requirements: 3 Limitations 4 Details: 5 Key Table: 6 The Default Animations: 6.1 Transitions: 6.2 Layer 3 Animations: 7 Programmers:

Description:

The Fade feature gives you the ability to fade or animate away from your front end, into a solid color or picture(s) of your choice. Meanwhile, the application will load in the background until the module calls for fade to exit or the application overtakes fade in fullscreen mode.

On exit of your application, Fade will attempt to fade or animate itself into focus, then exit the application and fade or animate back into your front end. The goal is to have a more pleasant transition between the front end and the application.

Requirements:

• Must use a module that has fade support.
• Must be enabled in your settings either globally, or for the system you want it on.
• Must have libraries and any other additional files in your Module Extensions folder.
• .NET Framework 3.5 or Visual C++ 2010 Redistributable Package installed for ZipHandler.dll support (this shows 7z progress during fade)

Limitations:

• True fullscreen applications will lock your video and will overtake Fade. This is by design and nothing you can do about it. It's up to you if you want to enable it for these systems or not. This does not happen in windowed or windowed fullscreen mode if your application supports it.
• Flickering can occur in true fullscreen applications when Fade is unable to overtake the application.

Details:

Create a folder in HyperLaunch\Media\Fade\Systemname\_Default. HyperLaunch will search and load images for each of its Layers if found. Example: HyperLaunch\Media\Fade\MAME\_Default\Layer 1.png

• Layer 1.png (This would show as the background image)
• Layer 2.png (This is a static image, and can be placed anywhere around the screen)
• Layer 3.png (This is a dynamic image of which can have an animation applied to it)
• Layer 4 (#).png (This is a set of images, when played, create an animation. One image = 1 frame. Frame 1 = "Layer 4 (1).png", frame 2 = "Layer 4 (2).png", and so on.)
• Layer -1.png (This would show as the background image during Fade_Out)

Optionally, you can place per-rom layer images in a subfolder named after the rom, and HyperLaunch will use it instead. This allows custom per-game images (like control images) to be shown before loading the game. Example: HyperLaunch\Media\Fade\MAME\88games\Layer 1.png

There is also a global fade image folder that HyperLaunch will look in if nothing is found in the system fade folder. This Fade_Image_Path is defined in the Global HyperLaunch.ini. Place any of the Layer # images in there to load when the above images are not found. Default Location: HyperLaunch\Media\Fade\_Default

Note: Transparency is supported on all images and on all layers. So if you are creative, you can have some very nice looking effects by utilizing the layering properties and settings.

Note 2: Image types supported are png, gif, bmp, and jpg. It is suggested you only use image types that support transparency however.


Key Table: