any reason why model importer doesnt support resources
This discussion was imported from CodePlex
mocaiv wrote at 2014-02-05 14:55:
Why do i have to have physical paths for all my obj and mtl files? i really dont want to deploy dozens of these model files to customers without first emedding them in a library. it appears the code supports physical paths only. After reviewing the code it would appear to be very simple to simply support streams and pulling from assembly resources. has anyone done this already before I add this myself?
objo wrote at 2014-02-05 15:16:
agree, it should be possible to provide a mechanism that loads the attached files from streams!
Customer support service by UserEcho