Endurion

Just to clarify: Just because send has a char* argument, doesn't mean you have to provide readable text.

You can directly send binary data as well.


Besides sending that thing over the net, the even worse performance problem will be formatting the floats to a string and back on the server. And now that string streams are introduced it's even got worse.

Since your floats are in a continuous buffer anyway, just send bufferData.

SetWindowPos does what you're looking for. Using the flags SWP_NOMOVE or SWP_NOSIZE you can control which parts of the call are actually done.

I think so, I'm not on Facebook anyway

Your AddOrder proc is always returning true. You should only return true, if you fully(!) handled a message, and false for everything else.

If you return true, Windows thinks the message is fully handled and doesn't do any default behaviour.

wären = (they) would have been
hätten = (they) would have had
würden = (they) would (do)

All "would"s as if they could if they wanted.

Samples:
Sie wären gerne einkaufen gegangen = They would have liked to go shopping.     (possible in the past)
Sie hätten gerne eingekauft = They would have liked to shop        (possible in the past)
Sie würden gerne einkaufen = They would like to shop           (possible in the future)

My translations to English are maybe not exact.

As mhagain pointed out. That:



IDirect3DDevice9* device = *(IDirect3DDevice9**)0xC97C28; // DirectX Device


will of course crash once you access the device; unless you're very very lucky to get the same pointer.

I assume you create the device in your main app and want to access it in your DLL? If so, you need to pass the app's device into the DLL, not rely on some random pointer value you once received.

iDontCare

Never ever give away the Debug folder. Debug usually consists of having specialized debug libraries included, which are simply not available on other peoples computer. If you pass on your game, always pass the Release build.

Depending on your dependencies you can get away with providing the binary and data files in a simple archive. You do have to make sure that you put the required dependencies in there too (in your case, the Tao framework resides in a assembly .dll).

If you're using Visual Studio there should be a option "Publish Project". This will create an installer project and usually automatically includes the dependencies as well.

The erase part is correct, he uses the iterator returned by it.  Check if you don't put an Actor in several ObjectLists (ie. it subscribed to several events), as you seem to only remove the actor from the current ObectList. In those cases you'd have invalid pointers in the other lists.

DirectSound still works nicely in Vista and later, you just have to allow software instead of hardware accelleration. The proper way is to check for hardware first, if that fails, fall back to software calculation.

Happy Birthday GD.net!



After all that time Flash still puts quite a big spike in the cpu meter ;)



And free rope for everyone!

Probably doesn't fix the problem, but you need to use the correct DC destroy functions:

For CreateCompatibleDC it's DeleteDC. For GetDC it's ReleaseDC.

Also, you do not have to create a new DC for every bitmap you want to blit. Think of a HDC as a device context (holds a bitmap, a brush, a pen, etc.). You can select a new bitmap in. Just make sure to finally select the first bitmap back in:

HDC backHDC = CreateCompatibleDC(hdc);
HBITMAP backbuff = CreateCompatibleBitmap(hdc, nclientWidth, nclientHeight);
HBITMAP hbmpOld = (HBITMAP)SelectObject(backHDC, backbuff);

// Draw the background
HDC hDisplayDC = CreateCompatibleDC(hdc);
HBITMAP hbmpItemOld = (HBITMAP)SelectObject( hDisplayDC , hbmpWorld );

if(!BitBlt(backHDC, 0, 0, nclientWidth, nclientHeight, hDisplayDC , 0, 0, SRCCOPY))
lastError = GetLastError();

// Draw the ball mask
SelectObject( hDisplayDC , redBall.GetCharacterMask() );

if(!BitBlt(backHDC, (int)redBall.Position.X, (int)redBall.Position.Y, redBall.GetCharacterInfo().bmWidth,
redBall.GetCharacterInfo().bmHeight, hDisplayDC, 0, 0, SRCAND))
lastError = GetLastError();

// Draw the ball
SelectObject( hDisplayDC , redBall.GetCharacter() );

if(!BitBlt(backHDC, (int)redBall.Position.X, (int)redBall.Position.Y, redBall.GetCharacterInfo().bmWidth,
redBall.GetCharacterInfo().bmHeight, hDisplayDC , 0, 0, SRCPAINT))
lastError = GetLastError();

SelectObject( hDisplayDC , hbmpItemOld );
DeleteDC( hDisplayDC  );

I've never used masks with GDI. You could try using TransparentBlt, which lets you use a color key.

This is probably what you're looking for: MSDN

However I find your statement that virtual keys shift around with keyboard layouts weird. That's the whole point of the virtual keys, they are defined constants and do NOT move around. The layout adjustment is done on a lower level, so a fixed string array should work fine.

Nah, that would make this thread funny. Can't have that happen.

Added growing algae and a bigger fish type. Yay me!