Nimble2D - All Comments

vbs cpu memory usage | Bookmarks URL

vbs cpu memory usage | Bookmarks URL — Wed, 22 Oct 2008 18:31:42 GMT

Pingback from vbs cpu memory usage | Bookmarks URL

re: Done Pondering, Shifting Gears

MattWorden — Sat, 27 Sep 2008 17:13:23 GMT

Thanks for checking in, Pascal.

Yep -- they are slow ... but the games I will be doing won't need too much along that line. During the pondering, I played around quite a bit with SDLdotNet as well -- but I didn't want to have to lock-in to its event-triggering system, plus the drawing routine slows down siginificantly when it involves alpha-blending.

Doing this will free me up from any external compatibility issues (if you can run .Net, you'll be able to run this) or framework, and I'll be able to just concentrate on getting the organizational pieces in place.

Later on, I'll just have to adapt the drawing code to match a new drawing system. My guess is that I will return to SlimDX (or something along those lines) at that point.

-Matt

re: Done Pondering, Shifting Gears

codeimp — Sat, 27 Sep 2008 11:02:41 GMT

Good luck. The graphics drawing in .NET is terribly slow. You should really continue with SlimDX. Or any other graphics library for that matter, because they all are better than the graphics in the .NET framework.

c convert to radians

c convert to radians — Tue, 24 Jun 2008 22:13:32 GMT

Pingback from c convert to radians

integer triangle

integer triangle — Fri, 16 May 2008 09:13:20 GMT

Pingback from integer triangle

re: Doing 2D in SlimDX

MattWorden — Mon, 10 Mar 2008 14:45:16 GMT

Hello ProgramIt!

Nice to hear from you. Yes ... VB.Net + SlimDX has gotten me excited as well. And my intention *is* to essentially replace DXGame (and extend a bit beyond it) as my main go-to toolset for 2D games.

We'll see if I can deliver! ;-)

-Matt

re: Doing 2D in SlimDX

Programit — Mon, 10 Mar 2008 06:15:54 GMT

Its good to see some new life in 2D!

Not since the DXGame days have I felt the 2D enthusiasm of programming with VB.

Reminds me of the DXGame days?

I'm looking forward to future developments!

re: Units of Measure

MattWorden — Wed, 27 Feb 2008 03:36:36 GMT

Good comments/questions, Pascal ... hope I do some justice in answering. I'll just take then them order.

First, the look-up-table-based trig library functions that I've alluded to are degrees-based ... mainly because I didn't want to do conversions back and forth. I have provided the trig functions that seem to matter for 2D games (sin, cos, GetAngle, GetComponents, etc.). The only reason I would provide an alternative "InRadians" would be for someone who wishes to use the original Math. namespace trig functions for some reason. Personally, I don't expect to use them ... just stick in degrees.

Second, I'm not sure what you mean on the color values. I have seen them represented in the 0-to-1.0 format and understand how they work. But when sticking to 0 to 255, and using the Color.ToARGB function ... things seem best in that range. Also, I've never done multiplication of color values. So, if you can give an example of when/where this might be used for a 2D library, then I might see the need to implement it differently.

Lastly, I personally like to work with alpha separately from the color values -- especially for sprites. I seem to mess around with the alpha value a *lot* more than with the color values. Usually, the color is just left at "White" while alpha is faded-in, faded-out, etc. Even in the case where I am using color-shading, I still do alpha separately. So, to be able to better handle it separately conceptually, I've split it out property-wise as well ... so I can just set MySprite.SpriteAlpha = 128, instead of having to build a full color each time I adjust the alpha.

re: Units of Measure

codeimp — Sun, 24 Feb 2008 20:44:51 GMT

Nice to see this is still progressing, I hope this really turns out in a successful library.

I'd like to point out some notes about your units of measure here;

- Angles are usually in radians for a reason: the whole goniometry mathematics are based on radians. Are you willing to convert between radius and degrees all the time?

- About the color values, why do you use 0 - 255? If you want to modulate one color with another, it is much easier when you use percentages (0 - 1). Sure a + b = c using both units. But when you do a * b with a 0..255 unit, you are likely get a value out of range which is not even the value you are looking for, you would have to do (int)((float)a * ((float)b / 255.0f)) and casting and dividing is not really what you want to do. With percentage units you do get the right value.

- A seperare propery with "Only" prefix that ignores the alpha component in the color? Why? If your users want 100% alpha they should just set the alpha component to 100%.

Doing 2D in SlimDX

Nimble2D — Wed, 13 Feb 2008 03:43:01 GMT

Now that I've had a couple of weeks to play around with 2D programming in Direct3D9 via SlimDX, here

re: A Nimble Launch

admin — Tue, 22 Jan 2008 17:10:10 GMT

Welcome Matt!

Pages tagged "nimble"

Pages tagged "nimble" — Sun, 20 Jan 2008 13:39:12 GMT

Pingback from Pages tagged "nimble"