Jump to content
  • Advertisement
Sign in to follow this  
hegel

SAS in DxViewer

This topic is 4487 days old which is more than the 365 day threshold we allow for new replies. Please post a new topic.

If you intended to correct an error in the post then please contact us.

Recommended Posts

it's pretty easy to load texture files for an .x file into memory first and then use D3DXCreateTextureFromFileInMemory to trace and render them when needed. But in DxViewer code sample from DirectX SDK 9, the create texture procedure is wrapped by sas. But sas doesn't provide any clue how to use D3DXCreateTextureFromFileInMemory. Anybody can give some suggestions on this sas problem?

Share this post


Link to post
Share on other sites
Advertisement
Well SAS just provides additional information to the application. It's still up to the application to manage the various resources. I've not looked at the source code for DXViewer, but I'd imagine it'll just pull out the filename and then load it using regular code...

hth
Jack

Share this post


Link to post
Share on other sites

You are right. Actually, SAS uses D3DXCreateTextureFromFileEx to load texture. But SAS check the path first, then it will choose whether to use that function. If in the path specified in .x file SAS can't find the texture files, it will not call D3DXCreateTextureFromFileEx. The path checking is done with a function named ResolvePath. I've commented out all the ResolvePath code in the DxViewer program, but this path resolving still works. It's really confusing. I just want to diable this texture path resolving function provided with SAS. Any idea?

Share this post


Link to post
Share on other sites
Sign in to follow this  

  • Advertisement
×

Important Information

By using GameDev.net, you agree to our community Guidelines, Terms of Use, and Privacy Policy.

Participate in the game development conversation and more when you create an account on GameDev.net!

Sign me up!