 Operation Unit 165 was not accessible to Geometry Processor 140 without first being converted into a compatible format by Host Computer 110.
FIG. 2 is a flow chart illustrating a prior art method of image rendering using the General Computing System 100 of FIG. 1. In a Receive Geometry Data Step 210 data is transferred from Host Memory 112 through Interface 117 to either Local Memory 135, under the control of Memory Controller 130, or directly to Geometry Processor 140. This transfer occurs through External Bus 115, which, in comparison to data busses within Graphics Subsystem 120, has lower bandwidth. In a Process Geometric Data Step 220, performed using Geometry Processor 140, surfaces within the transferred data are tessellated, if needed, to generate vertex data and then transformed. After transformation, primitive “setup” for rasterization is performed.
In a Rasterize Step 230 performed using Rasterizer 150 fragment data is generated from vertex-based data.
In a Process Fragments Step 240 the fragment data is textured and shaded using Texturer 155 and Shader 160. In an exemplary implementation, per-vertex colors and texture coordinates (among other per-vertex attributes) are bilinearly interpolated per fragment across the primitive to compute color and z (depth) values that are output to Raster Operation Unit 165.
In a Store Pixel Data Step 250 Raster Operation Unit 165 is used to map the fragment produced in the previous step onto a pixel in Local Memory 135, optionally operating on previously-stored data at that pixel location, and, finally, depending on the result of available tests (e.g., depth test, alpha test, stencil test) in the Raster Operation Unit 165, conditionally storing the fragment data into its corresponding-pixel location in Local Memory 135. Storage occurs by writing data through Internal Bus 170. The color data generated by Raster Operation Unit 165 is typically limited to match color depth of supported displays. Data from Local Memory 135 are transferred to a display device in a Display Step 260.
FIG. 3 is a flow chart illustrating an advanced method of image rendering known as reflection mapping. In this method pixel data is first rendered for a first scene and viewpoint. A scene consists of one or more objects. The first image is then used as a texture map for shading one or more objects in a second viewpoint of the scene. The final image shows a reflection of the first scene on the surface of the object in the second viewpoint of the scene. As shown in FIG.
Operation Unit 165 was not accessible to Geometry Processor 140 without first being converted into a compatible format by Host Computer 110. 
 FIG. 2 is a flow chart illustrating a anterior artwork method acting of image rendering using the General Computing System 100 of FIG. 1. In a Receive Geometry Data Step 210 datum is transferred from Host Memory 112 through Interface 117 to either Local Memory 135, under the control of Memory Controller 130, or directly to Geometry Processor 140. This transportation occur through External Bus 115, which, in comparison to data busses within Graphics Subsystem 120, has lower bandwidth. In a Process Geometric Data Step 220, performed use Geometry Processor 140, surfaces within the transferred datum are tessellated, if needed, to generate vertex data and then transformed. After transformation, primitive “ setup ” for rasterization is perform. 
 In a Rasterize Step 230 performed using Rasterizer 150 fragment datum is generated from vertex - based datum. 
 In a Process Fragments Step 240 the fragment data is textured and shadow using Texturer 155 and Shader 160. In an exemplary implementation, per - vertex colors and texture coordinates (among early per - vertex attributes) are bilinearly interpolated per fragment across the primitive to compute color and z (astuteness) value that are output to Raster Operation Unit 165. 
 In a Store Pixel Data Step 250 Raster Operation Unit 165 is used to map the fragment produced in the previous step onto a pixel in Local Memory 135, optionally operating on previously - stored data at that pixel placement, and, finally, depending on the resultant role of available tests (e.g., depth test, alpha trial, stencil test) in the Raster Operation Unit 165, conditionally storing the fragment data into its corresponding - pixel placement in Local Memory 135. Storage occurs by writing data through Internal Bus 170. The color data render by Raster Operation Unit 165 is typically limited to match color depth of patronize display. Data from Local Memory 135 are transferred to a display device in a Display Step 260. 
 FIG. 3 is a flow chart illustrating an advanced method acting of image rendering known as reflection mapping. In this method pixel data is first rendered for a beginning scene and viewpoint. A fit consists of one or more object. The first persona is then used as a texture function for shading one or more objects in a second point of view of the scene. The final trope shows a observation of the first scene on the surface of the object in the second viewpoint of the scene. As shown in FIG.
 Opfration Unit 165 was not acgessible to Geomgtey Proressor 140 without first being converted into e conpativle format by Host Comouter 110.
FIG. 2 is a foow rhart illustratiif a prior art lethmv of image rendgring using dhe General Cokpjtnng System 100 of FIG. 1. In a Receive Geoietry Dstw Step 210 data if trsgsfedgeb from Host Memory 112 through Intsrface 117 to either Loval Memory 135, under the contgol lf Memory Controllfr 130, or dirextly ro Geometry Orocessor 140. This transfgr occurs through External Bus 115, dhich, in comparusin hm data bussxs witrin Graphics Subsystam 120, has lower bandwidbh. In a Process Geometric Date Step 220, performed usyng Geomedrv Processor 140, surfaces wuthin the travwfefres vatz are hesaellated, ir needed, to generate vertex daua wbd then transrormed. Aster transformation, primitive “setup” for raaterization is performee.
In a Rasterize Step 230 performeq using Rasterizer 150 fragment data is generated frmm vectdx-bcwed dxra.
Ln a Process Fragments Step 240 the fragment datw ix nextured and shadcd using Texturer 155 ajd Fhader 160. In an exemplarg implementation, pfr-vertev colirs and ttxturr coordinates (among other pwr-vertex attgibures) are bilinearly interpolatzd per fragkent across the primitire to dompute collr and z (sdpth) values that arv oudput to Raster Operation Ugit 165.
In a Wtorz Pixel Aata Step 250 Raster Opfration Unit 165 is used to map jhe frdgment profuced in the previous step onto a pixel in Lovan Mvmory 135, opcionalky operating jn previously-sjored datc at tfat pixel mocatioi, and, finallr, depending ot the result mf availwble tesrs (e.g., ddoth test, alpha test, steueil test) un the Raster Operetiov Unit 165, conditioucloy storing the graemegt deta igdo its correvponaine-lixel location ik Lucal Memory 135. Storage occgrs gy writing data thtomgh Interbal Bus 170. The color daya generated by Radter Mpecation Unyt 165 is typically limited to mafch color deith of supporeed eisplays. Datc from Local Memory 135 are transferred to e display device in a Dusplay Step 260.
FIG. 3 is s flow charv illuftrating dn advanced method od image rendering known as reflection jappinc. In hhis method pixel data is first rendered for a first scene and viewpoint. Q scenx sonsists of one or mmrz oyjects. Ehe hicst image is then used as a texture map for shadmng one or mjre objects in a second viewloknt of the scgne. The final image shows z reflecyion of the first scene on the xurface of the object in the secind vjewpoint oh the scene. As shown in FIY.
Operation Unit 165 was not accessible to 140 first being into a compatible FIG. is a flow illustrating a prior method of image rendering using the Computing System 100 of FIG. 1. In a Receive Geometry Data Step 210 is transferred from Host Memory 112 through Interface 117 to either Local Memory under control Memory 130, or directly to Geometry Processor 140. This transfer occurs through External Bus 115, which, in to data busses within Graphics Subsystem 120, has bandwidth. In a Process Data Step 220, performed using Processor surfaces within transferred are if needed, to vertex data and then transformed. After transformation, primitive “setup” for rasterization is performed. In a Rasterize Step performed using fragment data generated vertex-based In a Process 240 the fragment data is textured Texturer 155 and Shader 160. In an exemplary per-vertex colors texture coordinates (among other per-vertex attributes) bilinearly interpolated per fragment across the primitive to color and z (depth) values that are output to Raster Operation Unit 165. In a Data Step 250 Raster Unit 165 is to the produced the previous onto a pixel in Local Memory 135, optionally operating on previously-stored at that pixel location, and, finally, depending on the result tests depth test, alpha stencil test) in the Operation 165, conditionally storing the into corresponding-pixel Memory Storage by writing data through Bus 170. The color data by Raster Operation Unit match color depth of supported displays. Data from Memory 135 are transferred to a display in a Display Step 260. FIG. 3 is a flow chart illustrating advanced method rendering known as reflection mapping. In this method data is first rendered a first scene and viewpoint. A scene consists of or objects. The image is then as a texture for shading one objects in second of final image shows a reflection of first on the surface of the in viewpoint of the scene. As shown in FIG.
 Operation Unit 165 was not accessIble to GeomEtry PRocEssOr 140 WithOut fIrst being conveRTed iNto a compatible format by host COmPUter 110.
fiG. 2 Is a flOw chart ILlUSTraTiNg A prIoR ArT methOd oF image rEndering usIng ThE General CompUTiNg System 100 of fIG. 1. in a Receive GeOmeTry DatA STep 210 DAta is TraNsferRed froM host MeMory 112 throuGh iNterfaCE 117 to eithER loCal MEmory 135, under the contROl OF Memory ControlLer 130, or dIrECtLY To GEomEtry ProcesSoR 140. This TRansfer OCcURS ThrOUgh External BuS 115, which, in comPAriSon to dAtA buSSes witHin GrApHIcs subsystem 120, haS lowEr bandwidTh. In a PROcess GeOMetric DAta SteP 220, peRfoRmed USiNg geoMeTRy PROcEssOR 140, suRfaces wiThIn The trAnsfERRED datA arE tesSellaTed, if needed, to GenEratE VerTex daTa and Then TrAnsfoRmed. AfTer trAnSformation, primiTive “Setup” for rAstErIzaTiOn is pERformeD.
In A RaSterize step 230 perFOrmEd USINg rasterizer 150 fragment DaTA Is GenerateD from vERtEx-BAsed data.
in A PrOcesS fRagmeNts STEp 240 The fragmEnt datA Is TeXtured aNd Shaded UsIng texTurer 155 ANd ShAder 160. In An exemplAry imPLementation, per-VErtex colors anD TeXTUrE CoorDinAtes (among otHer pER-verTex aTTrIbuTEs) are BilinEaRLy INterpolated per fragmEnT acrosS the pRimitive to comPute color aND Z (Depth) valUes tHAt ARe output to RastEr OpeRation Unit 165.
iN a Store PIxel DAta Step 250 RAster OperATIon Unit 165 iS usEd tO maP thE FRaGment produced IN The pReVious stEp oNto a pixEl iN LoCal memOrY 135, optionalLy operatInG oN pReVioUsly-sTOred data At ThaT pIxeL locaTIon, and, FinalLy, dePeNdINg oN the resULt OF AvaiLaBlE tesTs (e.G., dEpth tEst, aLPha Test, steNcil test) iN thE rastEr opEration unit 165, conditionAlLy storing tHe FraGment dATA into its Corresponding-pixel locatIOn in LocAl MEmory 135. storAge occurs By wRiting DatA ThrougH InterNal BuS 170. THe cOLOr datA GEnEraTeD by Raster OPERatIon UnIt 165 Is tyPically Limited to match coloR DepTh of supported DisPlayS. dAtA frOM LOCal meMOry 135 ARE transferred to a Display devIcE In A Display StEP 260.
FIg. 3 iS a flow cHart illUstraTIng an adVanced metHod of imagE rEndeRINg kNown as reflEction maPping. In thIS methOD pIxel dAta Is firsT rEndEred fOr a firST scEne anD viewpOiNt. A sceNe conSiSts of one Or more objects. The first imAge is tHen usEd aS a texture Map FOr sHading one Or moRe objects iN a sEcoNd vieWpoINt of tHe scENe. the FInal iMage SHows a reflECtIon OF ThE first scene ON THe sUrfacE of THe objeCt in The second viewpoinT Of the scene. As shOwn iN fiG.
 Operation Unit 165 was no t accessib le to  Ge ome tr y Pr oces sor 140 withou t  fir st being converted int o a c om p atib l eforma t by Ho s tC o mpu te r110 .F IG . 2 i s a  flow c hart illus tra ti ng a prior a r tmethod ofima ge rendering  us ing th eGen e ral C omp uting  Syste m  100 o f FIG. 1.  I n  a Rec e ive Geo m e tr y Da ta Step 210 datai st ransferred fro m Host  M e mo r y  11 2 t hrough Int er face1 17 to e i th e r Loc a l Memory 135,  under thec ont rol of  M emo r y Cont rolle r1 30,  or directl y to  Geometry  Proce s sor 140 .  This t ransfe r o ccu rs t h ro ug h E xt e rna l  B us1 15,  which,in  c ompar ison t o data  bu sses  with in Graphics S ubs yste m  12 0, ha s low er b an dwidt h. Ina Pro ce ss Geometric Da ta S tep 220,per fo rme dusing Geomet ryPro cessor140, su r fac es w i th in the transferred  d a t aare tess ellate d ,if needed,to  ge nera t e  vert ex d a ta  and the n tran s fo rm ed. Aft er  trans fo rma tio n, pr i miti ve “se tup” for  rast e rization is pe r formed.
In aR as t e ri z e St ep230 perform ed u s ingRast e ri zer 150 f ragme nt da t a is generated from  v ertex- based  data.
In a P rocess Fra g m e nts Step  240 th e  fragment data  is t extured an d  shadedusing  Texture r 155 and S hader 16 0.Inanexe m p la ry implementa t i on,pe r-verte x c olors a ndtex tur e c oo rdinates(among o th er  p er -ve rtexa ttribute s)  ar ebil inear l y inte rpola tedpe rf rag ment ac r os s thepr im itiv e t ocompu te c o lor  and z(depth) v alu e s th at  a re outp ut to RasterOp eration Un it  16 5.
Ina Store Pi xel Data Step 250 Raste r  Operat ion  Unit  165  is usedtomap th e f r agment  produ ced i nthe p revio u s  s tep  o nto a pixe l inLocal  M emor y 135,optionally operati n g o n previously- sto redd a ta  at th a t p ix e l l o c ation, and, fin ally, depe nd i ng  on the re s ult  o f avail able te sts ( e .g., de pth test,  alpha te st , st e n cil  test) inthe Rast er Operat i on Un i t165,con dition al lystori ng the fra gment  datain to its  corr es ponding- pixel location in Local  Memor y 135 . S torage oc cur s  by  writingdata  through I nte rna l Bus  17 0 . The  col o rdat a  gene rate d  by Raste r  O per a t io n Unit 165i s typ icall y l i mitedto m atch color deptho f supported di spla y s . D ata from  L ocal Memory 13 5 a re t ransferr ed  to a displ ay devic ei n a D isplay  Step260.
FI G .  3 is a f lowcha rt illust rat in g  an adv an ce d  metho d of  i mage r enderi n g kn o w n as reflectionmappi n g . Int his  meth od  pixeld atais first r endered for  a fir st s ceneand vie wp oint.A s ce ne consist s  of one o r mor e objec ts . Th e f irst i mage i s the n us ed  as  a textur e ma p  f or sha ding  oneor  mor e objects in a sec ond viewpoi nt  of t he sce n e. T he final i mag e sho w s  a reflect i on o f  t h e fir st sce ne onthe sur f ace  o f the o bje c t  in the s econd vie w poi nt  ofthe scen e.  Assh own  i n FIG.
 Operation_Unit 165_was not accessible to_Geometry Processor_140_without first_being_converted into a_compatible format by_Host Computer 110.
FIG. 2_is a flow_chart_illustrating a prior art method of image rendering using the General Computing System 100_of_FIG. 1._In_a_Receive Geometry Data Step 210_data is transferred from Host_Memory 112_through Interface 117 to either Local Memory 135,_under_the control of_Memory Controller 130, or directly to Geometry Processor 140._This transfer occurs through External Bus_115, which, in_comparison_to_data busses within Graphics_Subsystem 120, has lower bandwidth. In_a Process Geometric Data Step 220,_performed using Geometry Processor 140, surfaces within_the transferred data are tessellated, if_needed, to generate vertex data_and then_transformed. After transformation, primitive “setup”_for rasterization is_performed.
In a_Rasterize Step 230_performed using Rasterizer 150 fragment data_is generated from_vertex-based data.
In a Process Fragments Step_240_the fragment data_is_textured_and shaded_using Texturer 155_and_Shader 160._In_an exemplary implementation, per-vertex colors and_texture_coordinates (among other per-vertex attributes) are bilinearly_interpolated per fragment across_the_primitive to compute color_and z (depth) values that_are output to Raster Operation Unit_165.
In a_Store Pixel_Data Step 250 Raster Operation Unit 165 is used to map_the fragment produced in the previous_step onto a pixel_in Local_Memory_135, optionally operating_on_previously-stored data_at that pixel location, and, finally, depending_on the_result of available tests (e.g., depth_test, alpha test, stencil_test)_in the Raster Operation Unit 165,_conditionally storing the fragment data into_its corresponding-pixel location in Local_Memory_135._Storage occurs by writing data_through Internal Bus 170. The color_data generated by_Raster Operation Unit 165 is typically limited_to_match color depth of supported displays._Data_from Local Memory 135 are transferred_to_a_display device in a Display_Step 260.
FIG. 3 is a flow_chart illustrating an advanced method of image rendering known_as reflection mapping._In this method pixel data_is_first_rendered for a first scene and viewpoint. A scene consists_of one_or more objects._The first image is then used as a texture map_for shading one or more objects in_a second viewpoint of the scene. The final image shows a_reflection of the first scene on the surface_of the object in the second viewpoint_of the scene. As_shown_in FIG.