-
Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:
- Tag FS2020 specific questions with the MSFS2020 tag.
- Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
- Questions about aircraft design can be posted in the Aircraft design forum
- Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
- Questions about terrain design can be posted in the FS2020 terrain design forum.
- Questions about SimConnect can be posted in the SimConnect forum.
Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.
By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.
Windows Presentation Foundation (WPF)
- Thread starter Tim_A
- Start date
- Messages
- 34,981
- Country
Tim
There is some discussion of this in a thread in the Tools Programming Forum and I have moved this thread there
There is some discussion of this in a thread in the Tools Programming Forum and I have moved this thread there
Works well for standalone applications, unable to make work inside FSX (conflict at DirectX layer). Visual Studio 2005 has passable support for the 2D visual elements, and you'll really need VS2008 (the beta is available).
I was disappointed there is no designer for 3D although some can be purchased, and Blender has a XAML exporter (that must be tweaked to work).
There's great WPF info on the WPF blog ...
http://blogs.msdn.com/wpf3d/archive/2007/07/30/what-s-new-in-wpf-3-5.aspx
My overall impression is that I need to give this emerging technology some more time to mature - it has amazing potential UI wise with hardware accelerated graphics, and the tools make programming a bit more burdensome than they needs to be, unless you really like to edit raw XAML. A sign of immaturity is this incompatibility with layering of Direct3D spaces - hence the difficulty in using concurrently within the FSX process space.
Another issue I ran into inside the FSX process space has to do with the memory footprint - I blew right past the 2Gb per process limit on Windows XP with the CLR instanced inside the FSX process. That's not so much of a problem on 64bit XP or Vista, but you will have performance issues running a .NET based dll inside FSX on most machines unless they have 4Gb of memory - still well above today's average.
Etienne
I was disappointed there is no designer for 3D although some can be purchased, and Blender has a XAML exporter (that must be tweaked to work).
There's great WPF info on the WPF blog ...
http://blogs.msdn.com/wpf3d/archive/2007/07/30/what-s-new-in-wpf-3-5.aspx
My overall impression is that I need to give this emerging technology some more time to mature - it has amazing potential UI wise with hardware accelerated graphics, and the tools make programming a bit more burdensome than they needs to be, unless you really like to edit raw XAML. A sign of immaturity is this incompatibility with layering of Direct3D spaces - hence the difficulty in using concurrently within the FSX process space.
Another issue I ran into inside the FSX process space has to do with the memory footprint - I blew right past the 2Gb per process limit on Windows XP with the CLR instanced inside the FSX process. That's not so much of a problem on 64bit XP or Vista, but you will have performance issues running a .NET based dll inside FSX on most machines unless they have 4Gb of memory - still well above today's average.
Etienne
Last edited: