Graphics engines

Best engine for a huge scale 2-D rts+rpg-type game?

NVIDIA’s OpenGL can inter-operate with buffers and textures for either CUDA or OpenCL or DirectX or even OptiX. DirectX 11 can only interop with DirectX buffers and surfaces. This seems like a situation where OpenGL is clearly MORE functional than Direct3D. You can look at the NV_gpu_program5, NV_shader_buffer_load, and ARB_texture_buffer_object extensions to see how an OpenGL shader can read, and yes, even STORE to buffers.

OpenGL has plenty of features not available in DirectX 11 such as line stipple, accumulation buffers, immediate mode, display lists, smooth lines, access to shaders through both high-level shading languages (Cg or GLSL) as well as assembly language (NV_gpu_program5, NV_gpu_program4, ARB_fragment_program, etc.). And this all comes with cross-operating system portability, something DirectX 11 will never offer.

For example, OpenGL 4.1′s entire feature set, including programmable geometry and tessellation shaders and all the other DirectX 10 and 11 features are available on Windows XP as well as Vista and Windows 7.

OpenGL 4.1 supports both OpenGL and Direct3D conventions. So in Direct3D, you are stuck with the Direct3D provoking vertex or shader window origin convention, but with OpenGL 4.1 you can now pick your convention.

NVIDIA OpenGL has lots of ways it surpasses DirectX 11 in functionality such as support for bindless graphics (NV_vertex_buffer_unified_memory & NV_shader_buffer_load), arbitrary texture format swizzling EXT_texture_swizzle), Serial Digital Interface (SDI) video support (NV_present_video) including video capture (NV_video_capture).

BTW, you can get the actual PowerPoint slides from here:

http://www.slideshare.net/Mark_Kilgard/opengl-4-for-2010

(This slides are corrected and slightly expanded from the recorded presentation. For example, they include code for implementing adaptive PN triangles.)

ncurses

http://www.zen-cart.com/showthread.php?49239-Cookie-Usage-Must-be-Enabled

OP here, thanks. You guys are so helpful, someday I'll do something for you too. ;__;

>>5
You could start by sucking my dick.

>>6

The distances between us are way too big for your tiny pecker.

If Allegro is good enough for Xarn it ought to be good enough for you, too.

>>8
Please get rid of the ``cult of personality'' way of thinking. It is unscientific and ultimately destructive.

2D
write your own

>>10
lol you don't know shit

best?

use svg so everyone with a graphicañ browser can play it.

the Love game engine in Lua, or Actionscript for Flash

Here's a question, does any 3d accelerated application support multiple fullscreen windows? Also, can I draw two screen buffers into different windows, or would it almost be easier to have one main window, and the second window just read from a 3d buffer to a software buffer then draw that, since although you can't open multiple contexts you can draw to offscreen buffers?

>>15
On Windows, depending on your GPU drivers, you will be able to control each monitor as a separate Direct3D adapter. You can create a SwapChain for each monitor like that, and have multiple full screen windows.

With OpenGL on Windows and X11 alike (and probably OS X as well) you can do buffer sharing between contexts and either blit to monitors connected to different GPUs or create rendering contexts for all of them and render simultaneously.

At least in theory. None of these things actually work in real life, which is simply amazing considering that there are 3 huge hardware vendors all working on it; and they all suck monkey balls.

>>16
Why does programming have to be so difficult ;_;

Guess I might look at two of Irrlicht's examples, since it has a 2d example, a 3d ones, and multiple window example, as well as some basic stuff for managing context creation. If I could get the hello world example to work in two windows using separate cameras I'd be happy...

>>17
Why does programming have to be so difficult ;_;
We made it so.

>>17
The problem is with the lack of a proper buffer sharing mechanism. As long as your clients have only single GPU setups (CFX/SLI make one virtual GPU), this is just a matter of either:
D3D: creating multiple SwapChain classes for one Device.
OpenGL: creating two contexts and sharing a buffer handle between them.
On Direct3D, if you create a fullscreen Device, it will create one SwapChain per monitor automatically. On OpenGL you have to manually query and create a context per monitor. This ppt (lol, who has Windows these days) file will explain how to do it for OpenGL:
http://www.cs.uml.edu/~hmasterm/Charts/Managing_Multiple_Windows.ppt

On linux, we're working on solving this multi-GPU nightmare.

>>19
ty, I'll definitely take a read

didn't you ask this on /v/ early today?

I just wanted to point out to you bunch of pussies that roller coaster tycoon was written in assembly

>>21
Go the fuck back there and never come back