Bay 12 Games Forum

Okay, where do you all get all this moneys? When I was playing the game, I'd sell damn near everything and even at level 40 I had like 500g. Every time I get more than that, I see something shiny and buy it and am back to square one...

I'm really good at managing my money in real life, I guess it seems suiting that in a video game I absolutely suck at it.

Pfft, you guys think waaay too small: Mind control magic. Subtly you could easily bring all the worlds rulers to their knees. I'd let the world mostly carry on as normal, but have all the worlds powers secretly controlled by me. Keep it so nobody knows this, maybe make myself a mildly rich man who wants for nothing (extravagance isn't to my taste anyway). A nobody by many respects. But I'd use my powers to make sure things never went too far to shit, keeping everyone in a state of conflict without letting the conflict reach the point it risks out very species (no chance of nuclear war, for example).

Secretly, you shall have a lord, both powerful and magnificent. Terrible as the dawn, treacherous as the sea, all shall love me and despair! ^^

"New engine" is a marketing term. Game engines are a very generic and ill-defined concept. You write a game, and then you refactor a lot of the code so it can be used in a later game. This alone is often enough for the developers/publishers/marketing department to say that both games run on a modified version of the same engine, but that's no more or less valid a claim than saying because you made so many changes it's a new engine.

What they have done is rewritten a lot of the code they had. They have not thrown away any of the code that worked and did what they wanted, because that would have been stupid.

The same problem as oblivion of every random bandit running around in daedric armour or never seeing the weaker creatures again when you get to mid/high levels, I'd like one that would fix it.

Skyrim's is a lot tamer than that. You simply encounter more and more higher level bandits amongst the weaker bandits. They never get any "WTF why don't they sell this 60000g sword of uber awesome and just live like a king?" gear. Personally I'd rather they just do away with the level scaling almost completely, but that's because it doesn't go well with non-combat skills and you can easily get outclassed by enemies as punishment for selling too much loot and therefore levelling up your speech skill -_-

I think selling blood and plasma is illegal in the UK but don't quote me on that.

Actually a good way around the C++11 support for threads I've found is to, if it's not supported, bring boost's threading classes into the std namespace.

I've got a whole set of headers I've been working on that exist solely around faking C++11 features that are missing in.

Usually a float is a "single" as defined in IEEE 754, which is 32-bits.
Usually double is exactly what it says on the tin, two singles in size, 64 bits.
Usually a long double is some size bigger than a double. On GCC it is 80-bits I believe. Visual C++ just treats it as another double. This is why I say usually, the standard doesn't specify exact sizes or exact implementations so different compilers will do things differently.

The basic representation is the highest bit is the sign. You then have a series of exponent bits, followed by the fraction. 32-bit typically will have an exponent of 8-bits, and a fraction of 23 bits. 64-bit has 11 exponents and 52 fractions, hence the greater accuracy. Rounding errors can occur as not every number can be represented using this notation, like how we might have to simplify 1423.423543674574574564 to 1.4234e10^3. The more digits we can store in that representation, the closer to the true value we become.

You don't really ever need to worry about this until it bites you in the arse. Personally in C++ I'll always typedef the floats I'm using, that way if I ever encounter a problem with accuracy I can just change one line and see if that fixes things. You know how sometimes a physics simulation will just go crazy and explode? It's surprising how often that's due to a rounding error...

There are some things to be aware of in those situations, the main one being: Mixing very big and very small numbers together doesn't usually end well. 0.0000232342324 * 2423423524653 = omfgwtfisgoingonwhyiseverythingexploding? If you're doing this, revisit the scales and find some way to stop it. Fixing your timestep is always good. I personally have found it works well to ensure the timestep is always a multiple of a specific step, capping that multiple at a specific value and passing the remainder over to the next frame.