Visual Studio Graphics Tools - Content Pipeline - by Mateusz Migas

Status : 


Sign in
to vote
ID 785635 Comments
Status Closed Workarounds
Type Bug Repros 0
Opened 4/25/2013 9:26:36 PM
Access Restriction Public


After Visual Studio converts FBX file into CMO file seems like information regarding specular/specular power is missing. Tried on multiple files. 

Files generated with blender, both BINARY/ASCII, tested on VS2012 Express/Pro

Example file!KFRyFRKa!HZ9xTFF_LMUNktcRD8t5GAdpyO5omBb8QTpjiXSg-l0

A small tip:
By default Visual Studio sets the effect to Lambert which disables specular. You have to set the effect manually and specular properties for each material (regardless of which shader/effect you planning to use in your program). Which is impossible to do in Visual Studio Express Edition since you don't have Graphic Tools in there.

Can't see any link to uploaded file so adding other link just in case:!uRhjGIRJ!fQbDi2Z_lB2Vs_-6cVzy3gg3vVN6vriCw-PySEOI5pE
Sign in to post a comment.
Posted by DualOpAmp on 6/7/2013 at 7:39 PM
I've also noticed this problem with specular textures. I have an FBX file that contains both a diffuse texture and a specular texture. Yet when bringing the file into Visual Studio, the specular texture is not shown.
Posted by Jim [MSFT] on 5/3/2013 at 3:59 PM
Hi Lufiks,

Thanks for your feedback! We have added this bug fix request to our backlog and will consider a fix for it in a future version of Visual Studio.

Jim Griesmer
Visual Studio GPU and Graphics tools
Posted by Microsoft on 4/30/2013 at 3:30 AM
Hi Lufiks, thanks for your response. Your issue has been routed to the appropriate VS development team for investigation.
Posted by Mateusz Migas on 4/26/2013 at 3:26 AM
Added file and link to description.
Posted by Microsoft on 4/26/2013 at 2:25 AM
Thank you for submitting feedback on Visual Studio and .NET Framework. In order to efficiently investigate and reproduce this issue, we are requesting a demo project. We look forward to hearing from you with this information.
Posted by Macy [MSFT] on 4/25/2013 at 9:51 PM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(