File Release Notes and Changelog
Notes:
Recommended minimum configuration for advanced rendering examples:
DirectX 9.0c End-User runtime (http://www.microsoft.com/downloads/details.aspx?FamilyId=0A9B6820-BFBB-4799-9908-D418CDEAC197&displaylang=en )
32MB nVidia GeForce2 / ATI Radeon or better video card
1 ) Emma content examples:
C:\Program Files\Emma\demos
to get you started. Feel free to copy these .ema content examples and .lua scripts to your own workspace, and edit them to see what happens. To run unchanged, these examples will also need a local copy of the media assets they reference. These can be copied into your workspace from
C:\Program Files\Emma\demos\assets
2 ) Emma standalone applications and Emma activex control and Emma Mozilla plugin:
The Emma demos can be run by double-clicking the standalone applications:
C:\Program Files\Emma\emma.exe ( using its "Open" file dialog )
C:\Program Files\Emma\EmmaMFCApp.exe ( using its "Open" file dialog, or .ema, .lua or .luc files into its window.
or opening
C:\Program Files\Emma\demos\scenes\mainPluginTest.html
in Internet Explorer (using the Emma activex control ) or Firefox ( using the Emma Mozilla plugin ).
3 ) Documentation:
To help understand these examples, and to make changes to them, access the latest Content Development Kit documentation:
C:\Program Files\Emma\EmmaCDK.chm
or online, at:
http://www.emma3d.org/cdk
4 ) Keyboard shortcuts:
The following keyboard shortcuts are available ( of course, this window should have focus to receive keyboard input ):
1. The 'h' key prints help about keyboard shortcuts.
2. The 'o' key brings up the "Open" dialog box, to open another content file for viewing. ( emma.exe only )
3. The 'r' key reloads the current content file, restarting its animation. ( emma.exe only ) This shortcut offers a handy way to continuously preview edits you are continuously making to the same .ema or .liua source file.
4. The 'c' key opens the console if it is closed.
5. The 'p' key changes the rendering mode from points to wireframe to solid.
6. The 'l' key swaps the headlight on/off.
7. The 'i' key saves a screenshot into the content source directory.
8. The '=' key displays Emma framerate information
9. The '-' key displays Ogre statistics
10. The '0' key ( zero key ) displays a rudimentary Emma scene graph dump
11. The 'ESC' key exits the Emma standalone application.
(Built-in navigation will be available in version 0.5.)
5 ) Emma FAQs :
a ) General : http://emma3d.org/index.php?option=com_content&task=view&id=10&Itemid=25
b ) Content Development Kit : http://emma3d.org/index.php?option=com_content&task=view&id=11&Itemid=25
c ) Software Development Kit : http://emma3d.org/index.php?option=com_content&task=view&id=12&Itemid=25
6 ) For more on Lua, Emma's scripting language, see
http://www.lua.org/manual/5.0/
Our content examples make a lot of use of Emma's high-level media objects, or 'Nodes'. These are introduced in the online Content Developer's Kit documentation http://www.emma3d.org/cdk Browse the "Class Hierarchy" and "Class List" sections to get a sense of the Nodes which have been implemented to date; follow these links to each Node's Class Reference page to read about the Field interfaces which parameterize each Node's functionality.
7 ) You can get the Emma source code from
http://emma3d.org
8 ) Emma employs the Ogre rendering engine for its 3D capabilities. See
http://www.ogre3d.org
for more about Ogre. Readymade Ogre models, materials, images and other goodies suitable for use in Emma can be found under
C:\Program Files\Emma\demos\assets
9 ) Emma supports compiled lua binary files:
Do "Luac.exe foo.lua -o foo.luc" and then open foo.luc in Emma.
10 ) If you have any questions or comments, please go to Emma's project on SourceForge
http://sourceforge.net/projects/emma3d
or visit the Emma3d website
http://www.emma3d.org
and check out the discussion forums, file bug reports, etc.
Changes:
Release Notes :
1 ) Fusion, Emma's Lua-C++ integration package, has been split out into its own module.
You can now get Fusion separately from Emma, and use it in your projects where you need efficient integration between C++ and Lua.
2 ) Text2D node is now implemented.
Emma can now display "screen-aligned text" using the AntiGrain Geometry library (http://www.antigrain.com/). A much broader range of high-quality 2D rendering elements is scheduled to be implemented using this library.
A suite of input sensors have been implemented; these include:
3 ) ButtonSensor node provides keyboard and mouse button input from the user.
4 ) ValueSensor node provides valuator input (such as mouse position) from the user.
5 ) WindowSensor node provides an interface to the presentation window and its window system events.
6 ) VectorInterpolator node provides a powerful, efficient animation interpolator.
This can be used to import keyframed animation poses from modeling and animation tools, and interactively generate continuous inbetweens across these sampled poses.
7 ) Overloaded SFVec3f operators are now implemented:
The API for operator overloading has been improved to simplify its use. The operators +,-,*,/, unary minus and equals have been implemented for SFVec3f. For example, given that eye, center and up are SFVec3fs and stepSize is a float, the author can now write:
result = eye + (((eye - center):normalize()) * -stepSize)
You can also perform equality comparisons against tables like this:
f (result == {900,0,0}) then s = "Passed" else s = "FAILED" end
This approach can be applied to the other vector classes and where ever else it seems called for. See mainOperatorTest.ema to see the test in action...
8) WxGUI node has a greatly improved implementation.
A 'floating' field has been added to the WxGUI node. If this is true, the dialog floats as a modeless dialog. If this is false, the dialog is placed within the Emma window like an overlay and moves as part of the Emma window, whenever the Emma window moves.
WxWidgets node has been implemented to enable easy connection of GUI events and Emma objects.
9) Shape node now has a 'pickable' field.
This field supports a comprehensive interface for picking contained geometry and for adding content logic to the resultant picking events. See the CDK and sample content for examples of this new interface.
