record TIrrlichtCreationParameters

Type of the device.
This setting decides the windowing system used by the device, most device types are native to a specific operating system and so may not be available. idWin32 is only available on Windows desktops, idWindowsCE is only available on Windows mobile devices, idOSX is only available on Mac OSX, idX11 is available on Linux, Solaris, BSD and other operating systems which use X11, idSDL is available on most systems if compiled in, EIDT_CONSOLE is usually available but can only render to text, idAuto will select the best available device for your operating system. Default: idAuto.

Type of video driver used to render graphics.
This can currently be vdtNull, vdtSoftware, vdtBurningsVideo, vdtDirect3D8, vdtDirect3D9 and vdtOpenGL. Default: vdtSoftware

Size of the window or the video mode in fullscreen mode.
Default: 800x600.

Minimum Bits per pixel of the color buffer in fullscreen mode.
Ignored if windowed mode. Default: 16.

Minimum Bits per pixel of the depth buffer.
Default: 16.

Should be set to true if the device should run in fullscreen.
Otherwise the device runs in windowed mode. Default: false.

Specifies if the stencil buffer should be enabled.
Set this to true, if you want the engine be able to draw stencil buffer shadows. Note that not all drivers are able to use the stencil buffer, hence it can be ignored during device creation. Without the stencil buffer no shadows will be drawn. Default: false.

Specifies vertical syncronisation.
If set to true, the driver will wait for the vertical retrace period, otherwise not. May be silently ignored. Default: false

Specifies if the device should use fullscreen anti aliasing.
Makes sharp/pixelated edges softer, but requires more performance. Also, 2D elements might look blurred with this switched on. The resulting rendering quality also depends on the hardware and driver you are using, your program might look different on different hardware with this. So if you are writing a game/application with AntiAlias switched on, it would be a good idea to make it possible to switch this option off again by the user. The value is the maximal antialiasing factor requested for the device. The cretion method will automatically try smaller values if no window can be created with the given value. Value one is usually the same as 0 (disabled), but might be a special value on some platforms. On D3D devices it maps to NONMASKABLE. Default value: 0 - disabled

Whether the main framebuffer uses an alpha channel.
In some situations it might be desireable to get a color buffer with an alpha channel, e.g. when rendering into a transparent window or overlay. If this flag is set the device tries to create a framebuffer with alpha channel. If this flag is set, only color buffers with alpha channel are considered. Otherwise, it depends on the actual hardware if the colorbuffer has an alpha channel or not. Default value: false

Whether the main framebuffer uses doublebuffering.
This should be usually enabled, in order to avoid render artifacts on the visible framebuffer. However, it might be useful to use only one buffer on very small devices. If no doublebuffering is available, the drivers will fall back to single buffers. Default value: true

Specifies if the device should ignore input events.
This is only relevant when using external I/O handlers. External windows need to take care of this themselves. Currently only supported by X11. Default value: false

Specifies if the device should use stereo buffers.
Some high-end gfx cards support two framebuffers for direct support of stereoscopic output devices. If this flag is set the device tries to create a stereo context. Currently only supported by OpenGL. Default value: false

Specifies if the device should use high precision FPU setting.
This is only relevant for DirectX Devices, which switch to low FPU precision by default for performance reasons. However, this may lead to problems with the other computations of the application. In this case setting this flag to true should help on the expense of performance loss, though. Default value: false.

A user created event receiver.
It may be set later using the EventReceiver property as well.

Window Id.
If this is set to a value other than 0, the Irrlicht Engine will be created in an already existing window. For windows, set this to the HWND of the window you want. The windowSize and FullScreen options will be ignored when using the WindowId parameter. Default this is set to 0. To make Irrlicht run inside the custom window, you still will have to draw Irrlicht on your own. You can use this loop, as usual:

    while Run do begin              
        VideoDriver.BeginScene(True, True, 0);
        SceneManager.DrawAll;
        VideoDriver.EndScene;
    end;
            

Instead of this, you can also simply use your own message loop using GetMessage, DispatchMessage and whatever. Calling IrrlichtDevice::run() will cause Irrlicht to dispatch messages internally too. You need not call Device->run() if you want to do your own message dispatching loop, but Irrlicht will not be able to fetch user input then and you have to do it on your own using the window messages, DirectInput, or whatever. Also, you'll have to increment the Irrlicht timer. An alternative, own message dispatching loop without device->run() would look like this:

    var msg: MSG;
    ...
    while True do begin
            if PeekMessage(@msg, nil, 0, 0, PM_REMOVE) <> 0 then begin
                    TranslateMessage(@msg);
                    DispatchMessage(@msg);

                    if msg.message = WM_QUIT then break;
            end;

            // increase virtual timer time
            Timer.Tick;

            // draw engine picture     
            VideoDriver.BeginScene(True, True, 0);
            SceneManager.DrawAll;
            VideoDriver.EndScene;
    end;
            

However, there is no need to draw the picture this often. Just do it how you like.

Specifies the logging level used in the logging interface.
The default value is llInformation. You can access the ILogger interface later on from the IrrlichtDevice with getLogger() and set another level. But if you need more or less logging information already from device creation, then you have to change it here.