Efficiency

DirectX likes infrequent function calls. What strategies minimise function calls? eg if textures are grouped to save changeovers, there is limited size and some textures may be needed at more than one stage. But any sensible engine will do some kind of visibility testing so the set and order of models is not known. This situation invites lots of coincidence checking and texture state changes. ******** A Problem Worthy of Attack Proves It''s Worth by Fighting Back