(1 item) |
|
(1 item) |
|
(5 items) |
|
(1 item) |
|
(1 item) |
|
(2 items) |
|
(2 items) |
|
(4 items) |
|
(1 item) |
|
(6 items) |
|
(2 items) |
|
(4 items) |
|
(1 item) |
|
(4 items) |
|
(2 items) |
|
(1 item) |
|
(1 item) |
|
(1 item) |
|
(1 item) |
|
(1 item) |
|
(1 item) |
|
(1 item) |
|
(1 item) |
|
(2 items) |
|
(2 items) |
|
(5 items) |
|
(3 items) |
|
(1 item) |
|
(1 item) |
|
(1 item) |
|
(3 items) |
|
(1 item) |
|
(1 item) |
|
(2 items) |
|
(8 items) |
|
(2 items) |
|
(7 items) |
|
(2 items) |
|
(2 items) |
|
(1 item) |
|
(2 items) |
|
(1 item) |
|
(2 items) |
|
(4 items) |
|
(1 item) |
|
(5 items) |
|
(1 item) |
|
(3 items) |
|
(2 items) |
|
(2 items) |
|
(8 items) |
|
(7 items) |
|
(3 items) |
|
(7 items) |
|
(6 items) |
|
(1 item) |
|
(2 items) |
|
(5 items) |
|
(5 items) |
|
(7 items) |
|
(3 items) |
|
(7 items) |
|
(16 items) |
|
(10 items) |
|
(27 items) |
|
(15 items) |
|
(15 items) |
|
(13 items) |
|
(16 items) |
|
(15 items) |
Ah, the tyranny of peer pressure.
A while ago I wrote a conversion utility that
takes DirectX '.x' mesh files (well, some of them) and converts them to XAML mesh definiitions. However,
there have been a number of breaking changes to
the 3D support in Avalon in the recent CTP release
rendering my program less useful.
Due to popular demand (well, demand from as many as 2 people, although that may well be 100% of the user community) I am pleased to present DXMeshToXamlv1.1.zip (76K). This is almost identical to the previous version - the main differences are:
Hardware DirectX device, because for some reason, asking for the Reference
device now fails on my laptopNOTE: all the same caveats apply as with the previous version, so please go and read about that before using this.
Also, note that if you use Chris Anderson's useful little XamlPad utility, you'll rapidly discover that it doesn't much like extremely long lines of text. And sadly, my converter produces some heroically long lines of text. (That's mainly because of the vast number of coordinates packed into a single XML attribute.) So if you want to try this with anything other than trivial models, I'd use VS.NET rather than XamlPad to play about with this stuff.)