next »

[Layl]

The easiest way to learn what radians are is to just look at a few examples next to the constant Tau.
I try to avoid ever notating radians in flat numbers because that doesn't say much, it's much easier to see when you put Tau next to it.

Tau = 2*Pi

Half a circle: Tau * 0.5
Quarter of a circle: Tau * 0.25
One tenth of a circle: Tau * 0.1

It's much easier to work with than a 0-360 range.

[oahda]

It's theoretically simpler but most of us are so used to degrees that we can do it in our sleep anyway. To me, they're equally easy. I prefer degrees, tho – probably because I learned those first, and no better reason than that. I use pure radians on rare occasions when I do certain sine wave stuff.

[Layl]

Previously my game engine would use a Dictionary lookup to find an IVertexRenderer to call to render vertices. Each IVertexRenderer would have GL.VertexAttribPointer calls hardcoded.

Now, my game engine instead uses reflection to detect the attributes of a vertex type and automatically builds up a GL.VertexAttribPointer call.

The changes are still really early and dirty and there's a lot it can't do yet but I'm really pleased with the fact that I can now just throw in any vertex type I want without effort.

[deathbeam]

After long time I figured out how to handle multi-threading in Mozilla Rhino (JavaScript implementation in Java). I am soo happy that I can use networking finally

[Photon]

I made quarters of a circle graphic cycle on the screen!!!



Translation: I got basic animations working in my entity-component system, as well as basic linking of said animation to its appropriate entity. Its been great getting things hammered out and flowing nicely, and I'm pleased to say that my basecode (for #1GAM and future endeavors) is getting in shape. I may even have something usable for April's Ludum Dare if I participate.

[Boreal]

I just discovered that glVertexAttribPointer() has been replaced with a better API since OpenGL 4.3.  Along with glBindVertexBuffers(), introduced in OpenGL 4.4, I can implement a data-oriented renderer in a much more direct and simple way.

Basically, before this new API, even if you had a ton of objects with the same vertex/instance format but different buffers, you'd need to have a VAO for each buffer combination.  Now you can use a single VAO, set up the vertex/instance format once, and only use one call to bind the buffers for each object.

[Quarry]

and then you realise the amount of people with drivers and hardware incompatible with 4.X

[Abnormal Ape]

I have written "hello world" for the first time in my life about a month ago, after deciding giving creating my dream game a shot. It's all the fun I've hoped for, and more. I'm basically spending my days thinking "what would be fun?" which has to be one of the most awesome things to do, period. Programming truly is magic; I say it and it is so (pending proper syntax and spelling lol).

[Boreal]

and then you realise the amount of people with drivers and hardware incompatible with 4.X

Eh, I suspect that by the time I actually release a game hardware adoption will have caught up.  Even then, it's not like I can't make compatibility branches since checking if a feature is supported is incredibly easy with GLEW.

[Miziziziz]

I've been programming something for the last few hours. Suddenly I encounter some major bugs, and then, after a couple of minutes of working on something completely unrelated, the bugs are fixed and everything works perfectly.
Kinda scared, honestly.

[oahda]

The best part is when a clean fixes everything because some object files have gotten kind of incompatible but still not enough for the program not to compile and run. Then it crashes.

I had an interesting case the other day, where adding two member variables – and not even using them for anything beyond setting their values in the constuctor – to a class made my submarine game crash when turning on the light.

The problem was related to accessing the Box2D world instance for raycasting, giving me a segmentation fault. As I had inserted the two variables before the one holding this world instance, the RAM position of which relative to the other members thus would have moved. But it seems not enough recompilation happened in order to notify other parts of the code accessing this class of this, so that they were trying to access the world variable in a position now occupied by other variables and so crashing. Cleaning the project and recompiling everything again did the trick.

I suppose this is more of a grumpy programmer post, but yeah, it was a reply to the above post~

It's the "restart your computer/device" solution of programming.

[rundown]

yesterday i found my harddrive again that contained 2 years of work, I worked almost every evening on my engine.
Kinda got depressed that I lost it. But REJOICE! I found it again. i'll be making more backups now.

So yea, so happy!

[Rusk]

yesterday i found my harddrive again that contained 2 years of work, I worked almost every evening on my engine.
Kinda got depressed that I lost it. But REJOICE! I found it again. i'll be making more backups now.

So yea, so happy!

So not only did you get your work back, you ended up with an extra hard drive. That has got to be a higher power telling you to backup!

[rundown]

yesterday i found my harddrive again that contained 2 years of work, I worked almost every evening on my engine.
Kinda got depressed that I lost it. But REJOICE! I found it again. i'll be making more backups now.

So yea, so happy!

So not only did you get your work back, you ended up with an extra hard drive. That has got to be a higher power telling you to backup!

Well that basicly was the reason why i bought the harddrive in the first place. I misplace so mutch xD I'm gonna glue it to my desk!

[ThemsAllTook]

I just repurposed some old collision code from a scrapped game project, translated it from 2D to 3D, simplified it from 503 lines down to only 206 total, and it works even better than before. I feel enlightened.

[InfiniteStateMachine]

The easiest way to learn what radians are is to just look at a few examples next to the constant Tau.
I try to avoid ever notating radians in flat numbers because that doesn't say much, it's much easier to see when you put Tau next to it.

Tau = 2*Pi

Half a circle: Tau * 0.5
Quarter of a circle: Tau * 0.25
One tenth of a circle: Tau * 0.1

It's much easier to work with than a 0-360 range.

Never thought to do that. That's pretty cool. I'm gonna have to try thinking like that in the future.

I've just become so accustomed to radians over the years that degrees started to look foreign.

[Sik]

Got IUP to work, now I can make standard GUIs \o/ (needed this to make the launcher for Sol, it's tricky getting it to look as I want but with other libraries it'd be much harder)

[Shadowspaz]

Hopefully, I'll start getting more active on the forums (again... I come and go), so I'll start here, since the "Happy Programmer Room" is the exact place I belong right now- I've got a group!

For the first time since I started my gamedev career 5ish years ago, I no longer need to worry about designing sprites, or music, or dialog choices. As the sole programmer in a group consisting of three artists, I now have completely free reign over the turn-based battle system in our RPG, the spellcrafting system we'll be implementing (and absolutely everything else), without ever needing to worry about the non-code sides of things. It feels great.

The game we're making will have a pretty strong 'Chrono Trigger' feel to it, with some 'Dragon's Dogma' elements in the story, combined with art inspired by 'Sword Art Online.' I'll probably start a devlog once there's actually something to show, so it's a bit early for that, but... I had to say something...

[powly]

glVertexAttribPointer() has been replaced with a better API

Which one? Cannot find anything related to this.

[starheap]

I managed to get some decent performance increases(100% in some cases) in our 2d python game by moving some code over to cython. We are probably gonna switch to C++ at some point...