Beta
Upcoming SlideShare
Loading in...5
×
 

Beta

on

  • 180 views

 

Statistics

Views

Total Views
180
Views on SlideShare
180
Embed Views
0

Actions

Likes
0
Downloads
1
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Beta Beta Document Transcript

  • 3D-Analyzer - 22.07.2002Supplemental Readme Document, Rev. 0.94-------------------------------------------3DAnalyze.exe : Control Application V1.5dat1.000 : DirectX(r) DX8 Core d3d8.dlldat2.000 : OpenGL(r) Core opengl32.dllLiesMich.txt : ReadMe (German)ReadMe.txt : ReadMe (English)releasenotes.txt : Version Historybeta.txt : Supplemental Information (this file)Copyright ( 2002 Tommti Systems )All Rights ReservedTommti Systemshttp://www.tommti-systems.comthomas@tommti-systems.com=======================================================================Whats in this distribution?=======================================================================This distribution contains the Beta Release for public testing oftarget Applications.NOTE: DirectX 8.1 redistributable files must be used with this Tool!=======================================================================Disclaimer=======================================================================This Software is provided "as is" for the sole purpose of evaluation.Tommti Systems can not be held liable for any damage this program mightcause. It is an unfinished, partly implemented Program meant for betatesting only. Use at your own Risk!=======================================================================Installation=======================================================================Requirements------------- Windows 95,98,ME,2000,XP- PC with a Direct3D capable VGA Card- 1 GigaByte of free Harddisk space if Debug Logging is desired (warrants approx. 150 seconds of live Debug time)=======================================================================Capabilities and Limitations=======================================================================The 3D Analyzer Tool was created and refined to overcome limitationsposed by modern 3D Games and other Applications on several currentmainstream 3D Cards.Basic functionality will equip non-T&L cards with a software substitute.Advanced functionality will enable User selectable 3D Features notavailable in many older Cards.
  • Yet, this is presently achieved not by Emulation but by NUL-Rendering.This means, advanced 3D Features the Card is not capable of, are reportedas available in Hardware, but have their calls intercepted and therespective 3D Features will not be rendered.These functions are based upon the premise and ideas, that :- 3D Games can be launched, that otherwise would fail due to lack of Hardware support.- No 3D Game should solely rely on a few, isolated rendering features, and therefor loss of image quality by NUL-Rendering should be minimal and acceptable in most cases.=======================================================================Overview=======================================================================This version is based on the original V1.3 but has been extended incapabilities to workaround 3dfx-specific limitations.It is used for Beta testing to aid in future development.Feel free to use on any DirectX8 or DirectX8.1 Application for testing.This Version is provided "as is" and is currently lacking fullyoperational implementation of desired features. It currently containsUser selectable options, some of which use can cause the targetApplication to behave severely abnormal, crash or fail otherwise.Before using this Program, make sure all other Programs are closed.Note - Classic Options are explained in the standing V1.4beta ReadMe.=======================================================================Whats new ?=======================================================================The V1.3 Version has been found to fail with many target Applicationswhen used with 3dfx Voodoo based Cards.A "Hardware Limits" Block of Options have been created for eachworkaround required to overcome 3dfx Voodoo specific limitations,as explained below:- Emulate HW TnL capsEffect :This Option will Enable the basic DirectX 8.1 core Emulation.Status :FunctionalLimiting Factors :Will be recognized only by DirectX8 or DirectX8.1 applications.- Emulate Cube Maps capsEffect :This Option will report Cubic Mapped BumpMapping Hardware capabilityto the target Application.Status :FunctionalLimiting Factors :
  • Any surface utilizing this Effect will not be rendered. This canlead to mis-colored Textures, as the Texture beneath is displayedunmodified.Future Goals :undeterminedfull Software Emulation is pending evaluation and/or prove-of concept- Emulate Pixel Shader capsEffect :This Option will report DirectX 8 compilant Vertex and Pixel ShaderHardware capability to the target Application.Status :FunctionalLimiting Factors :Surfaces utilizing this effect will be rendered faster, but with lowerTexture detail, as no true Pixel Shader features are being rendered.- Emulate Bump Map capsEffect :This Option will report full BumpMapping and Envroinment MappedBumpMapping Hardware capability to the target Application.Status :FunctionalLimiting Factors :Any surface utilizing this Effect will not be rendered. In some cases,this can lead to strongly mis-colored Textures (rainbow effect) as theoriginal BumpMap is displayed unmodified.Future Goals :undeterminedfull Software Emulation is pending evaluation and/or prove-of concept- Emulate Max. sim. TexturesEffect :This Option will report full single-pass, 4-layer MultitexturingHardware capability to the target application.Status :FunctionalLimiting Factors :This Option will cause applications to use 4-layer Multitextures, ofwhich only 2 will be effectively rendered. This will result in untexturedand uncolored Objects, on which 4-layer Multitexturing is applied.In some cases, basic envroinmental Rendering techniques such as Lightmapsmight not be rendered, causing undue decrease in visual Quality.Future Goals :undeterminedPossibly create a workaround to render a full, second multitexture pass,or comparable rendering techniques as substitute.- Emulate other DX8.1 capsEffect :This Option will enable DirectX 8 Driver compatibility masking,
  • regardless of actual Driver compatibility. It will also enable theadvanced DirectX 8.1 Emulation core.Status :limited FunctionalLimiting Factors :Advanced DirectX8.1 Advanced Pixel Shader capability has not been fulyimplemented yet. An Application accessing Advanced Pixel Shadercapabilities can either behave severely abnormal or crash.Future Goals :undeterminedPossibly achieve full Advanced Pixel Shader capabilities by CPUemulation.=======================================================================Developer Features=======================================================================A Debug Option is included in this Release.It should only be used for aquiring vital Debug information and is setto Disabled by default.When to use :- Applications failing to initialize or give Error Messages- Applications reporting missing Hardware Support where some should be (recheck selected Emulation Options)- Applications exert severly abnormal behaviour not caused by known Limiting FactorsHow to use :Depending on selected Application and .dll Directories, a log.out anda shader.out are generated, as soon as the Application is launched.Shader.out is presently not implemented and will maintain a file sizeof 0 Bytes.Before debugging, prepare the Application to launch only the 3D scenein question, if possible. This will isolate the problem as much aspossible, and keep file size to a minimum.If an Application generates its own specific Logfiles, these should beretained for additional analysis as well.Warnings :----------When Debug Logging is active, upto several MegaBytes of DebugInformation per Second can be generated! Depending on workload on the3D Analyzer Tool, this can lead to excessive HardDrive I/O operations.The Performance hit when using debug logging can be as significant asslowing 3D rendering down to well less than 1 frame per second!Do NOT allow Debug File to exceed available remaining Harddrive space!This can lead to severe crashes, and will render the debug file useless!One can expect (depending on rendering complexity) upto 400MB perMinute live rendering time.Hints :Even very large (1000 MegaByte) LogFiles can be very effectivelycompressed, using common Software like WinZIP, WinRAR or WinACE.1000 MegaBytes will result in an approx. 12MB compressed Filesize.
  • =======================================================================Misc. Information=======================================================================This Readme complements the standing V1.4 beta Readme File.Effective use of this Tool requires full understanding of the embeddedFeatures and Limiting Factors.When encountering errors or malfunctions, make sure these errors can bereproduced, and are not caused by any unrelated component of your system.This includes running Applications, which minimum requirements are notfully met even with the use of 3D Analyzer.-----------------------------------------------------------------------This document is subject to change, and may stand to be verified andcorrected by the Developer.Alpha-Testing conducted by :FalconFlyfalconfly@ewetel.nethttp://www.falconfly.deAmigaMerlinAmigamerlin@3dfxzone.ithttp://www.3dfxzone.itDocument generated in support by FalconFly, 08/06/2002