Search Results for "requirements"

...Take advantage of motorized-head file. Easy to integrate in your Renderfarm System. Add specific rules to select the most suitable machines regarding CPU, RAM, GPU requirements of each Node.

Dos Doom with 3d floors, slopes, destructible architecture, demo compatibility 1.9, fast speed youtube https://goo.gl/pbNybV Requirements: 486DX, 4MB RAM Win95, 8MB Dos(run -ram8mb parm) https://goo.gl/agT2wc https://goo.gl/3EFVBg Recommended: 486DX4 100MHz, 16MB RAM https://goo.gl/IWGLkQ Run on Dos,Win9x, XP 7 32 bits, Dosbox Turbo Android requires Dosbox: Win 64bit or WinXP w/ some video drivers https://goo.gl/FE6rRF Bugs: command line needs one space after wad or other parm to work right: cdoom -file s4 -warp 1 save config fault sometimes, glitches in rendering slopes due to fixed point usage, line of sight bullets error on slopes,sprites in multi 3dfloors sometimes render wrong similar to duke nukem 3d quake heretic hexen vavoom zdoom gzdoom but not compatible,only doom2 doom run Thanks:id software for original doom code https://www.idsoftware.com MBF authors,Vladimir Arnost for muslib 1.80: http://www.fit.vutbr.cz/~arnost/welcome.html

Java implementation of a software renderer. Software rendering is handled only by a CPU, without any GPU support. Renderer is implemented in pure Java, without any additional frameworks. Additional requirements: JDK / JRE 8

...page_id=12 for complete descriptions and package downloads VolTK is a free C++ Toolkit that implements a tri-layer volume rendering framework, which is designed to meet the requirements of both algorithm research and application assemblage. Features * Tri-layer volume rendering * CPU implementation: multi-threading supported * GPU implementation: CUDA based implementation * CPU-GPU correspondance * Both low level interfaces and high level interfaces are provided * Replace the components easily with your own design * Various rendering modes: MIP/Isosurface/Full volume rendering * Endoscopy interaction mode implemented * Pre-integration supported * Cross platform (windows and RHEL tested)

...The goal was to make each object "know" how it should be displayed and changed, so that a simple GUI tool can display complex objects, and new objects can be created without having to spend time creating the "widgets" for them. The basic requirements was: - The "GuiObjects" don't know which graphical toolkit (e.g. gtk) will be used to display them. - The objects can be displayed without knowledge of what exactly they are. - save/load/undo/etc. will be taken care of automatically. In addition, because this is a project I started to train in C++: - there will be no dynamic casting! ...