This is Huge! (for me)
-
Started looking at incorporating "Storyboards" (WPF/UWP) into my UWP "frame based" app. Didn't know how to accommodate both at the same time originally (different "time lines"), but things are becoming more clear. Just so I didn't paint myself into a corner, I created 400 rectangles to test my conclusions. Then assigned 400 different "story boards" to each rectangle, then started them moving all at the same time. "Smooth as butter" and negligible CPU. (UWP has a separate composition thread that runs "independent" of the UI thread "if" you create "independent" (of layout) timelines / storyboards; which inludes moving and rotating). In other words, I think (raw) UWP and C# make a great games platform.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
Started looking at incorporating "Storyboards" (WPF/UWP) into my UWP "frame based" app. Didn't know how to accommodate both at the same time originally (different "time lines"), but things are becoming more clear. Just so I didn't paint myself into a corner, I created 400 rectangles to test my conclusions. Then assigned 400 different "story boards" to each rectangle, then started them moving all at the same time. "Smooth as butter" and negligible CPU. (UWP has a separate composition thread that runs "independent" of the UI thread "if" you create "independent" (of layout) timelines / storyboards; which inludes moving and rotating). In other words, I think (raw) UWP and C# make a great games platform.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
How about a short article or tip? Would be useful for the rest of us.
-
Started looking at incorporating "Storyboards" (WPF/UWP) into my UWP "frame based" app. Didn't know how to accommodate both at the same time originally (different "time lines"), but things are becoming more clear. Just so I didn't paint myself into a corner, I created 400 rectangles to test my conclusions. Then assigned 400 different "story boards" to each rectangle, then started them moving all at the same time. "Smooth as butter" and negligible CPU. (UWP has a separate composition thread that runs "independent" of the UI thread "if" you create "independent" (of layout) timelines / storyboards; which inludes moving and rotating). In other words, I think (raw) UWP and C# make a great games platform.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
MS does promote UWP as a game development UI, but not with C#... C# can be a performance problem if the game is demanding... And of course UWP as a MS only realm...
"If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization." ― Gerald Weinberg
-
MS does promote UWP as a game development UI, but not with C#... C# can be a performance problem if the game is demanding... And of course UWP as a MS only realm...
"If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization." ― Gerald Weinberg
UWP compiles to ARM. Runs on XBox. MS is getting more stuff running on Android. Things don't look as bleak as when I was coding in Visual FoxPro. As for performance, my timer based frame rate is 20 FPS, and everything I need to do I am able to do in 50 ms with enough to spare. And this is a "big" demanding app. EV's these days have 1000HP; is one with 600HP a performance problem?
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
How about a short article or tip? Would be useful for the rest of us.
My search for "help" found very few where I was threading. It seems in its architecture, MS only considers "one time" or "forever" animations. It's a bit of voodoo to get your zombies back. I'd be doing more apologizing than providing helpful advice. We'll have to see how it ends; but it is actually reducing my code base since I was starting to write my own "slaves" (before realizing it). Instead of "threads", I can feel somewhat confident about unleashing a few hundred "storyboards".
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
