Stand-alone Executable & Browser Applet Generator for 3D Rad

The 3D Rad Compiler utility allows you to generate a distributable, stand-alone version of your 3D Rad (.3dr) projects.

The output can be a standard Windows program (stand-alone executable) or an applet playing in a webpage at your website.

In either case, the compiled product doesn't require 3D Rad to be installed on the final user's machine.

As a stand-alone executable it can run windowed, maximized or in full-screen at any resolution supported by the video-card, including wide-screen formats. Full-screen modes allows for a smoother framerate.

When playing in a browser, your projects will still support all the functionality of a regular application, including, for example, network gaming, game settings persistence, ability for the user to remap game controls and so on.

The compiler can combine multiple projects into more complex applications where each project can be called by others to achieve, for example, multi-level games. Please see ExitFade object documentation for details.

FUNCTIONS

Add Project
Click this button to add a new .3dr project to the list of projects to compile.

The project list is on the left of the window. To mark a project as the entry point, double click it.

Remove Project
This button removes the currently selected project from the list of projects to compile.

Compiled Project Name
Click in the edit box and specify a name for the compiled executable.

Can run windowed
Check this option to allow users of your stand-alone project to choose whether to run it in windowed mode or full-screen. If this option is not checked, they will only be able to select a full-screen display.

NOTE: this setting is ignored when the compiled project plays in a browser (embedded into a webpage, see Embed at, below).

Maximized
Check this option to make your stand-alone project run in a borderless, maximized window. Unlike full-screen modes, this mode will allow final users to switch between background applications without terminating your compiled project.

NOTE: this setting is ignored when the compiled project plays in a browser (embedded into a webpage, see Embed at, below).

Adaptive GFX
Check this option to minimize the size of loaded textures when users of your stand-alone project select a display size smaller than 640x480 pixels. This will likely reduce rendering quality, but it can dramatically improve frame-rate and make your project playable on slower systems.

NOTE: this setting is ignored when the compiled project plays in a browser (embedded into a webpage, see Embed at, below).

Compiled Project Icon
Click the Browse button and select an icon (.ico) file to use for the compiled executable.

NOTE: this setting is ignored when the compiled project plays in a browser (embedded into a webpage, see Embed at, below).

Global loading image
Click the Browse button and select a .jpg image file to use as loading screen for the compiled executable. Note that the image will be stretched to fit the screen, if necessary. Recommended image size is 1024x768 or bigger.

This image will only be displayed while loading projects that don't have their own specific loading image.

To associate a loading image with a project, you must save a .jpg file with the same name as the project, to the

C:\3D Rad\3DRad_res\projects

folder. For example, a loading image for a project called MyProject.3dr must be named MyProject.jpg.

You can also associate a sequence of images to a project, so that they are shown like a slideshow while the project loads, by saving the images with their file names numbered. For example, MyProject.jpg, MyProject_002.jpg, MyProject_003.jpg, MyProject_004.jpg is a valid image sequence. Note that the first image has no number ad that the second image is _002. There is no _001 image.

When using image sequences, keep in mind that the total number of objects in the project is used as basis to try to split the loading time evenly among the images. The actual loading time cannot be used as a reference because it cannot be determined before the project is actually loaded.

As a consequence, certain images may be displayed for longer than others, based on what kind of objects are loaded while they are shown.

To associate a music loop to a project, so that it is played while the project loads, you must save a .wav or .ogg file with the same name as the project, to the same folder. For example, a loading music loop for a project called MyProject.3dr can be named MyProject.wav or MyProject.ogg.

Loading progress-bar
Check this option to display a progress-bar while the standalone project loads.

The progress bar is shown at the lower edge of the screen, over the loading image (see above).

In your compiled projects, you can customize the progress bar aspect by modifying the
.\3DRad_res\system\progressBar.dds
file.

You can also use a different image format by opening the progressBar.x file with an ASCII editor and changing the 'progressBar.dds' name to your alternate image file (must be .dds, .png, .tga, .bmp or .jpg).

Include third-party runtimes
Check this option to allow the standalone project to work on Windows�-based systems that do not have the latest Microsoft� updates or the latest NVidia� PhysX� system software installed. Please see license file for important information.

Embed at
Check this option to compile your project to a browser applet.

After compilation (see Compile, below) all you have to do is upload the 3 generated files to your website.

The exact location at your website must be specified in the input box before compilation. For example: http://www.3drad.com/ or http://www.3drad.com/subdir/

The URL to launch the compiled applet will be the specified website location followed by the uploaded .htm page name (for example http://www.3drad.com/StuntPlane.htm or http://www.3drad.com/subdir/StuntPlane.htm).

IMPORTANT: to the specified website location you must also upload the OSAKitPro.CAB and the OSAKitProPlayer.exe files.

These files are free plug-ins developed by AncientSoft and they must be present on the server to allow visitors of your website to play your compiled 3D Rad projects in their browser.

A complete SDK and a commercial version of the plug-ins, offering several advantages, including the ability to certify the embedded applet by using your own digital signature, is available at the OSAKit website.

To all 3D Rad users, Ancientsoft is currently offering a 10% discount (coupon code: 3DRAD10).

Prompt
Check this option to always let visitors of your applet page know and authorize the launch of the OSAKit plug-in, when they are on Window XP or Windows Vista with UAC disabled.

Enabling this option, which de-activates the OSAKit plugin after every use, is highly recommended because letting an application run in the browser without giving visitors a chance to block it, in case they don't trust the website, isn't a wise security policy.

DISCLAIMER: 3D Rad author is not affiliated in any way with AncientSoft and is not responsible for any damage caused by the OSAKit plug-in or its use. Use of the OSAKit plugin will be at your own risk.

Save Settings
Allows you to save the current compiler settings.

Load Settings
Allows you to load a previously saved settings file.

Clear List
Clears the list of projects to compile.

Help
Opens this help document in your default Web browser.

Compile
Generates the stand-alone executable (or the browser embeddable files) in a sub-folder within the specified destination folder. The sub-folder name will be the compiled project name plus a time-stamp (YYYYMMDDHHMMSS format).

For stand-alone executables, the compiled project can be run by double-clicking the .exe file in the destination sub-folder. To port the compiled project to another PC, simply port the destination sub-folder and its contents.

For browser applets, you need to upload the compiled files to your website (see Embed at, above).

PROTECTING COMPILED CONTENTS
Compiled .3dr files are protected so that they cannot be opened and examined in the editor by the final user.

Note that compiling a 3D Rad project only protects the .3dr (project) file. It does not protect any resource files (3d models, textures, sounds etc) and the protection applied to the .3dr file is not designed to stop serious hacking attempts.

In order to fully protect your compiled projects and all the resources you can use third party tools, like 3D Rad V-Packer, specifically developed to protect 3D Rad compiled projects.


	WHAT IS 3D RAD? CLICK HERE TO FIND OUT!			3D Rad Compiler The 3D Rad Compiler utility allows you to generate a distributable, stand-alone version of your 3D Rad (.3dr) projects. The output can be a standard Windows program (stand-alone executable) or an applet playing in a webpage at your website. In either case, the compiled product doesn't require 3D Rad to be installed on the final user's machine. As a stand-alone executable it can run windowed, maximized or in full-screen at any resolution supported by the video-card, including wide-screen formats. Full-screen modes allows for a smoother framerate. When playing in a browser, your projects will still support all the functionality of a regular application, including, for example, network gaming, game settings persistence, ability for the user to remap game controls and so on. The compiler can combine multiple projects into more complex applications where each project can be called by others to achieve, for example, multi-level games. Please see ExitFade object documentation for details. FUNCTIONS Add Project Click this button to add a new .3dr project to the list of projects to compile. The project list is on the left of the window. To mark a project as the entry point, double click it. Remove Project This button removes the currently selected project from the list of projects to compile. Compiled Project Name Click in the edit box and specify a name for the compiled executable. Can run windowed Check this option to allow users of your stand-alone project to choose whether to run it in windowed mode or full-screen. If this option is not checked, they will only be able to select a full-screen display. NOTE: this setting is ignored when the compiled project plays in a browser (embedded into a webpage, see Embed at, below). Maximized Check this option to make your stand-alone project run in a borderless, maximized window. Unlike full-screen modes, this mode will allow final users to switch between background applications without terminating your compiled project. NOTE: this setting is ignored when the compiled project plays in a browser (embedded into a webpage, see Embed at, below). Adaptive GFX Check this option to minimize the size of loaded textures when users of your stand-alone project select a display size smaller than 640x480 pixels. This will likely reduce rendering quality, but it can dramatically improve frame-rate and make your project playable on slower systems. NOTE: this setting is ignored when the compiled project plays in a browser (embedded into a webpage, see Embed at, below). Compiled Project Icon Click the Browse button and select an icon (.ico) file to use for the compiled executable. NOTE: this setting is ignored when the compiled project plays in a browser (embedded into a webpage, see Embed at, below). Global loading image Click the Browse button and select a .jpg image file to use as loading screen for the compiled executable. Note that the image will be stretched to fit the screen, if necessary. Recommended image size is 1024x768 or bigger. This image will only be displayed while loading projects that don't have their own specific loading image. To associate a loading image with a project, you must save a .jpg file with the same name as the project, to the C:\3D Rad\3DRad_res\projects folder. For example, a loading image for a project called MyProject.3dr must be named MyProject.jpg. You can also associate a sequence of images to a project, so that they are shown like a slideshow while the project loads, by saving the images with their file names numbered. For example, MyProject.jpg, MyProject_002.jpg, MyProject_003.jpg, MyProject_004.jpg is a valid image sequence. Note that the first image has no number ad that the second image is _002. There is no _001 image. When using image sequences, keep in mind that the total number of objects in the project is used as basis to try to split the loading time evenly among the images. The actual loading time cannot be used as a reference because it cannot be determined before the project is actually loaded. As a consequence, certain images may be displayed for longer than others, based on what kind of objects are loaded while they are shown. To associate a music loop to a project, so that it is played while the project loads, you must save a .wav or .ogg file with the same name as the project, to the same folder. For example, a loading music loop for a project called MyProject.3dr can be named MyProject.wav or MyProject.ogg. Loading progress-bar Check this option to display a progress-bar while the standalone project loads. The progress bar is shown at the lower edge of the screen, over the loading image (see above). In your compiled projects, you can customize the progress bar aspect by modifying the .\3DRad_res\system\progressBar.dds file. You can also use a different image format by opening the progressBar.x file with an ASCII editor and changing the 'progressBar.dds' name to your alternate image file (must be .dds, .png, .tga, .bmp or .jpg). Include third-party runtimes Check this option to allow the standalone project to work on Windows�-based systems that do not have the latest Microsoft� updates or the latest NVidia� PhysX� system software installed. Please see license file for important information. Embed at Check this option to compile your project to a browser applet. After compilation (see Compile, below) all you have to do is upload the 3 generated files to your website. The exact location at your website must be specified in the input box before compilation. For example: http://www.3drad.com/ or http://www.3drad.com/subdir/ The URL to launch the compiled applet will be the specified website location followed by the uploaded .htm page name (for example http://www.3drad.com/StuntPlane.htm or http://www.3drad.com/subdir/StuntPlane.htm). IMPORTANT: to the specified website location you must also upload the OSAKitPro.CAB and the OSAKitProPlayer.exe files. These files are free plug-ins developed by AncientSoft and they must be present on the server to allow visitors of your website to play your compiled 3D Rad projects in their browser. A complete SDK and a commercial version of the plug-ins, offering several advantages, including the ability to certify the embedded applet by using your own digital signature, is available at the OSAKit website. To all 3D Rad users, Ancientsoft is currently offering a 10% discount (coupon code: 3DRAD10). Prompt Check this option to always let visitors of your applet page know and authorize the launch of the OSAKit plug-in, when they are on Window XP or Windows Vista with UAC disabled. Enabling this option, which de-activates the OSAKit plugin after every use, is highly recommended because letting an application run in the browser without giving visitors a chance to block it, in case they don't trust the website, isn't a wise security policy. DISCLAIMER: 3D Rad author is not affiliated in any way with AncientSoft and is not responsible for any damage caused by the OSAKit plug-in or its use. Use of the OSAKit plugin will be at your own risk. Save Settings Allows you to save the current compiler settings. Load Settings Allows you to load a previously saved settings file. Clear List Clears the list of projects to compile. Help Opens this help document in your default Web browser. Compile Generates the stand-alone executable (or the browser embeddable files) in a sub-folder within the specified destination folder. The sub-folder name will be the compiled project name plus a time-stamp (YYYYMMDDHHMMSS format). For stand-alone executables, the compiled project can be run by double-clicking the .exe file in the destination sub-folder. To port the compiled project to another PC, simply port the destination sub-folder and its contents. For browser applets, you need to upload the compiled files to your website (see Embed at, above). PROTECTING COMPILED CONTENTS Compiled .3dr files are protected so that they cannot be opened and examined in the editor by the final user. Note that compiling a 3D Rad project only protects the .3dr (project) file. It does not protect any resource files (3d models, textures, sounds etc) and the protection applied to the .3dr file is not designed to stop serious hacking attempts. In order to fully protect your compiled projects and all the resources you can use third party tools, like 3D Rad V-Packer, specifically developed to protect 3D Rad compiled projects.