View Forum Thread

> Forum Home > Announcements > Some features already coming in Smedge 3 version 2.5

	Mon, 06/Apr/2009 3:56 PM
Robin 1138 Posts	These features are already implemented or are in development and testing currently: True system-wide "default" Engine, Engine presets, and Product Presets The "Save to Default" and "Presets" buttons allow you to save as a system-wide default for all users. Also, new users and new Engines automatically download and use these defaults when they connect, so there is zero configuration time for new installations. Just run the installer, and it's done. Maxwell pyramid merging. This will allow you to render Maxwell MXIs across your farm, and have each machine intelligently merge only what it needs to, in order to minimize the amount of network traffic caused by moving the giant files around. Job local file copying. Using the new parameter command .CopyLocally, you can get a filename translated to a local temporary directory for the Job. The only files in the directory are files that Job requested to be copied, and they are automatically deleted when the job is finished. Max Module scene file local copying Using the job local file copying, the Max module now can copy the max scene file to the local temp folder. This eliminates Max's scalability problem reading scene files when using more than 50 machines at a time. New Work Events - WorkPostExecuteSuccessfulEvt and WorkPostExecuteUnsuccessfulEvt These events are called immediately after the WorkPostExecuteEvt, but only if the work was either successful or unsuccessful, respectively. The events are called synchronously with the work, so no new work will start until the even process has finished. File Server system Smedge now has a built in file server system. This system can be accessed via the API only at this time. This allows arbitrary direct transfer of any file (with appropriate permissions) from any client machine to any other. Threading and buffer optimizations Smedge performance should be more reliable due to tuning done to the prioritization and memory buffers used during operation. Some of the bug fixes: Smedge can now start any number of After Effects processes Though there are still some limitations on how After Effects can be used because it is tied to the GUI application, there was a conflict between Smedge and the 32 bit AErender process when running on 64 bit Windows, probably caused by a bug in the Microsoft 32 bit emulation library. This has been worked around, and could, in theory, also improve other 32 bit applications when run on 64 bit Windows, if they happen to have the same particular conditions that After Effects has. GUI crashes caused by library issues on OS-X and Linux Master crashes caused by the Generic Script Module Loading Job files never respected the "paused" state. The Submit Job window will now remember if the last job you submitted was paused. $(WaitForJobID) now returns the ID, instead of just 0 or 1.
	Tue, 07/Apr/2009 2:20 PM
QuakeMarine1 177 Posts	sound great

Page 1 of 1