#directx 11

[techworldsports]

DirectX 11 Setup

View On WordPress

[misfitgames]

Rendering Refactors

Since much of the last phase was about rendering, it isn’t surprising that the refactors are mostly rendering related too. For the rendering portion of my code I’ve been following the DX11 tutorials on RasterTek.com and that’s been useful, but not very generalized. A couple small refactors I made today was to change my shader files to be .hlsl and to remove the DXTexture class. For DXTexture, I moved its data into DXRenderable and its logic is now in a couple of utility functions. The reason for this change is that DXTexture is basically just a class that wraps some data and utilities. Instead of having to keep that in mind, I’d rather just have all the DX data in Renderable and keep the utils in a namespace to themselves for use as needed.

The bigger issue on my mind is that I’m not really happy with my current handling of raw vertex data, renderable creation, and shader creation. Right now I have Verterx and VertexUV, ColorShader class and TextrueShader class, and separate (but almost identical) Renderable creation methods for color and texture. Renderable is holding onto a Vertex* and a VertexUV* and using them based on if the texture is set or not, which is terrible. Basically a lot of problems stemming from slapping together separate shader pipelines.

I spent about an hour today breaking down where my render data is, who holds on to what, and what each is responsible for. I think I have come up with a plan to consolidate all these issues and hopefully make the renderable creation and drawing process more flexible. I’ll be working on that as part of this end-of-phase refactor time through the holidays.

[macdailynews]

Macworld reviews Parallels Desktop 15 for Mac review: Metal makes this one for the gamers

Macworld reviews Parallels Desktop 15 for Mac review: Metal makes this one for the gamers

With Parallels Desktop, you can run Windows, Linux and other popular operating systems and applications on your Mac without rebooting. Parallels Desktop 15 for Mac includes: Support for DirectX 11, leveraging macOS Catalina innovations, additional Mac integration points, new virtualized hardware, performance increases and lots more.

View On WordPress

[magzier-blog]

Path Of Exile Is About To Drop Itself Out Supporting Window XP and Windows Vista Operating System Anymore

This may sound thoroughly cruel to all the fanboys and diehards of obsolete Windows XP and Windows Vista operating system - but they have been cornered for a few years, and recently what they are rooting for received a mortal blow from Path of Exile. Based on the earlier announcement from Path of Exile publisher Grinding Gear Games, the game will no longer support Windows XP and Windows Vista System in two months. Starting this project off by launching the major update of the game on March: 3.6.0 patch, the game will finally weed out these two out-of-date PC operating systems along with the old renderer: DirectX 9, while it still provides a two-month-long preparation time for all the players who still hang on to the "antiques" to digest and move on to update the new versions of them, or get rid of the game for good instead.

This decision made by Grinding Gear Games isn't out of impulse at all. Based on the information and details given by the official announcement, we are able to find out that, after Microsoft ceased the mainstream support for Window XP and Windows Vista respectively in 2009 and 2012, and most of the game publishers, developers, as well as PC games' stores like Steam successively gave up on the support over them, it absolutely makes sense for Grinding Gear Games to follow suit in the end. And even dragging the audiences and users of Path of Exile into the final decision, it doesn't add in the rationality of overruling the previous plan at all, given that there is only 0.1% of players in Path of Exile still insisting on adopting these old operating systems nowadays.

In addition to highly suggest the users upgrade to a secure version of Windows, which they obviously should have done that for years, Grinding Gear Games also indicated that unlike the Window XP and Windows Vista systems, they are keeping its hands off withdraw any support of the "32-bit clients for users of 32-bit versions of Windows", however on the other hand, strongly recommend them switching to 64-bit clients for the sake of technology advances.

As for making a choice between the old DirectX 9 renderer and the current mainstream DirectX 11 renderer, the company seems a lot more resolved than the divided crowd in Path of Exie as there are tons of players favoring of the latest version of the renderer and others doesn't. According to the statement made by Grinding Gear Games, the group of users intending to advocate the old renderer are only obsessed with the functionality it performs to disable and filter the shadows in the game out. However, as the company's statement goes, this kind of functionality causes nothing but disruptions to the crucial portion of the gameplay and the inner environment, as well as jeopardizing the design concept and the significance of the existence of in-game shadows.

Is this the only reason why Grinding Gear Games quit the support for DirectX 9 at all? I am afraid not. Things can go much further than as expected in this case. As the company is able to "free up some technical resources for other more impactful tasks" and "simplify a lot of code", from casting both the old Windows operating systems and the old renderer off, the doom for those outdated seems indisputably inevitable and raring. Unity and concentrated allocation definitely make the development of the game much easier than it used to be for the devs team. Taking into account the benefits the company itself will garner from this project, this may be the last straw for Grinding Gear Games proactively throwing the oldish software away in no time.

MMOAH.com now opened up a New POE Currency store and welcome all the gamers have been yearning for POE Orbs, Items, and other POE Currency in new Betrayal League. Take a look at the new store, if you purchase now, you will be given a coupon code - "BETRAYAL" for free, which can save you 6% off for every order on MMOAH.

[canlitvizle-blog1]

DirectX 11 İndir

DirectX 11 indir

Tek Tıkla Son Sürat DirectX 11 Ful indir

(more…)

View On WordPress

[itukikikuti]

Windows APIでウィンドウを出す

最初はウィンドウを出してみましょう。ウィンドウがないとゲームで何が起こってるのか全然わかりませんからね。Visual StudioでC++の空のプロジェクトを作ってください。それからSource.cppというファイルを作ってください。別にSource.cppという名前じゃなくてもいいですけどね。

// Source.cpp int main() { return 0; }

これがC++における最小のコードですよね。このmain関数がエントリーポイントと言ってプログラムのスタート地点です。知らない人の為に全部説明していきますよ！実行したらコンソールウィンドウが出ます。

さて、Windows APIではCreateWindowでウィンドウを作ってShowWindowでウィンドウを表示するとウィンドウを出せます、ざっくりいうと。

// Source.cpp #define OEMRESOURCE #include <windows.h> int main() { HINSTANCE instance = GetModuleHandleW(nullptr); WNDCLASSW windowClass = {}; windowClass.lpfnWndProc = DefWindowProcW; windowClass.hInstance = instance; windowClass.hCursor = (HCURSOR)LoadImageW(nullptr, MAKEINTRESOURCEW(OCR_NORMAL), IMAGE_CURSOR, 0, 0, LR_SHARED); windowClass.lpszClassName = L"GameLib"; RegisterClassW(&windowClass); HWND handle = CreateWindowW(L"GameLib", L"GameLib", WS_OVERLAPPEDWINDOW, 0, 0, 640, 480, nullptr, nullptr, instance, nullptr); ShowWindow(handle, SW_SHOWNORMAL); return 0; }

具体的にはこんな感じのコードを書きます。へぇこう書くのか、くらいに思っとけば大丈夫です。ぶっちゃけ私も定型文くらいにしか考えてませんし、全部覚えてないので書くときは自分の過去のコードとか見て書きます。Windows APIを使うのでWindows.hをインクルードします。#define OEMRESOURCEというのは、12行目のOCR_NORMALを使えるようにするためのものです。

そしてメインループというものも書きます。ゲームループと言ったりもします。メインループがないとウィンドウが出たと同時にアプリケーションが終わってウィンドウも消えてしまいます。

… ShowWindow(handle, SW_SHOWNORMAL); while (true) { MSG message = {}; if (PeekMessageW(&message, nullptr, 0, 0, PM_REMOVE)) { if (message.message == WM_QUIT) break; TranslateMessage(&message); DispatchMessageW(&message); } else { // ここにゲームの処理を書いていく } } return 0; }

ShowWindowの下にメインループの下にメインループを書きました。return 0;は一番最後の行にないとダメです。メインループの前にreturn 0;があるとメインループの前にアプリケーションが終わるので意味が無いです。PeekMessageWとかTranslateMessageとかDispatchMessageWはウィンドウメッセージの処理です。これをしないとウィンドウを動かしたり、大きさを変えたり出来ません。実行してみましょう！ウィンドウ出ましたね！

コンソールウィンドウを消す方法もあります。実はWindowsのアプリケーション専用のエントリーポイントというものがあって、int main()をint APIENTRY wWinMain(HINSTANCE, HINSTANCE, LPWSTR, int)に変えて実行すると普通のウィンドウだけ出せます。このWinMainというのがWindows専用のエントリーポイントです。

さて、ウィンドウのサイズを幅640ピクセル、高さ480ピクセルにしてるんですが、実は出来てないんです。640x480という風にしてしまうと、ウィンドウのタイトルバーとかウィンドウの枠とかも含めて、640x480になってしまうんです。それに、ウィンドウの位置も左上になってしまってますから、中央にしたほうが良いです。SetWindowPosを使えばウィンドウの位置と大きさを変えられます。

… HWND handle = CreateWindowW(L"GameLib", L"GameLib", WS_OVERLAPPEDWINDOW, 0, 0, 0, 0, nullptr, nullptr, instance, nullptr); RECT windowRect = {}; RECT clientRect = {}; GetWindowRect(handle, &windowRect); GetClientRect(handle, &clientRect); int w = (windowRect.right - windowRect.left) - (clientRect.right - clientRect.left) + 640; int h = (windowRect.bottom - windowRect.top) - (clientRect.bottom - clientRect.top) + 480; int x = (GetSystemMetrics(SM_CXSCREEN) - w) / 2; int y = (GetSystemMetrics(SM_CYSCREEN) - h) / 2; SetWindowPos(handle, nullptr, x, y, w, h, SWP_FRAMECHANGED); ShowWindow(handle, SW_SHOWNORMAL); …

こんな感じでCreateWindowWの下に書きました。位置と大きさの計算がちょっとややこしいですね。CreateWindowWに渡していた0, 0, 640, 480は0, 0, 0, 0に変えてます。

あとはウィンドウプロシージャーも書いておきましょう。今はウィンドウの右上のＸボタンを押してもアプリケーションが終わりません。ウィンドウプロシージャを書けばそれが治ります。

LRESULT CALLBACK ProceedMessage(HWND window, UINT message, WPARAM wParam, LPARAM lParam) { if (message == WM_DESTROY) PostQuitMessage(0); return DefWindowProcW(window, message, wParam, lParam); }

こういう関数を書いてwindowClass.lpfnWndProc = DefWindowProcW;をwindowClass.lpfnWndProc = ProceedMessage;にすれば出来ます。DefWindowProcWはデフォルトで用意してあるウィンドウプロシージャです。それとは別に自分でウィンドウプロシージャを用意できます。それが上の関数です。自分でウィンドウプロシージャを書くと例えばウィンドウの大きさが変わったらこうするとかウィンドウが消えたらどうするとか自分で処理を追加出来ます。

では、今までのコードをクラスにしてみましょう。Window.hppとWindow.cppというファイルを作ってください。

// Window.hpp #pragma once #define OEMRESOURCE #include <windows.h> #include <directxmath.h> class Window { public: static void Initialize(); static HWND GetHandle(); static DirectX::XMINT2 GetSize(); static void SetSize(int width, int height); static bool Update(); private: static const wchar_t* name; static HWND handle; static LRESULT CALLBACK ProceedMessage(HWND window, UINT message, WPARAM wParam, LPARAM lParam); };

// Window.cpp #include "Window.hpp" const wchar_t* Window::name = L"GameLib"; HWND Window::handle; void Window::Initialize() { HINSTANCE instance = GetModuleHandleW(nullptr); WNDCLASSW windowClass = {}; windowClass.lpfnWndProc = ProceedMessage; windowClass.hInstance = instance; windowClass.hCursor = (HCURSOR)LoadImageW(nullptr, MAKEINTRESOURCEW(OCR_NORMAL), IMAGE_CURSOR, 0, 0, LR_SHARED); windowClass.lpszClassName = name; RegisterClassW(&windowClass); handle = CreateWindowW(name, name, WS_OVERLAPPEDWINDOW, 0, 0, 0, 0, nullptr, nullptr, instance, nullptr); SetSize(640, 480); ShowWindow(handle, SW_SHOWNORMAL); } HWND Window::GetHandle() { return handle; } DirectX::XMINT2 Window::GetSize() { RECT clientRect = {}; GetClientRect(handle, &clientRect); return DirectX::XMINT2(clientRect.right - clientRect.left, clientRect.bottom - clientRect.top); } void Window::SetSize(int width, int height) { RECT windowRect = {}; RECT clientRect = {}; GetWindowRect(handle, &windowRect); GetClientRect(handle, &clientRect); int w = (windowRect.right - windowRect.left) - (clientRect.right - clientRect.left) + width; int h = (windowRect.bottom - windowRect.top) - (clientRect.bottom - clientRect.top) + height; int x = (GetSystemMetrics(SM_CXSCREEN) - w) / 2; int y = (GetSystemMetrics(SM_CYSCREEN) - h) / 2; SetWindowPos(handle, nullptr, x, y, w, h, SWP_FRAMECHANGED); } bool Window::Update() { MSG message = {}; while (PeekMessageW(&message, nullptr, 0, 0, PM_REMOVE)) { if (message.message == WM_QUIT) return false; TranslateMessage(&message); DispatchMessageW(&message); } return true; } LRESULT CALLBACK Window::ProceedMessage(HWND window, UINT message, WPARAM wParam, LPARAM lParam) { if (message == WM_DESTROY) PostQuitMessage(0); return DefWindowProcW(window, message, wParam, lParam); }

// Source.cpp #include "Window.hpp" int APIENTRY wWinMain(HINSTANCE, HINSTANCE, LPWSTR, int) { Window::Initialize(); while (Window::Update()) { // ここにゲームの処理を書いていく } return 0; }

こんな感じでクラス化してみました。Initialize関数でウィンドウ出して、Update関数がメインループを回してます。GetHandleとかGetSizeは他のところで使いそうなので書いておきました。 ダウンロードしたい人はGitHubにサンプルリポジトリがあるので、ぜひダウンロードしてください。 </directxmath.h></windows.h></windows.h>

[ansiklomedia]

Star Wars Battlefront Sistem Gereksinimleri Belli Oldu

Star Wars Battlefront Sistem Gereksinimleri Belli Oldu

8 Ekim’de Açık Beta’sı başlayacak olan Star Wars Battlefront’un sistem gereksinimleri Origin üzerinde ortaya çıktı.

İşte oyunu oynamak isteyenlerin sahip olması gereken bileşenler.

Star Wars Battlefront Oynuyoruz videomuz için tıklayın…

Minimum PC Sistem Gereksinimleri:

İS: 64-bit Windows 7 veya üstü

İşlemci (Intel): Intel i3 6300T veya eşdeğer

Bellek: 8GB RAM

Sabit Disk: En az  40GB boş alan

E…

View On WordPress

[ansiklomedia]

Mafia 3 Sistem Gereksinimleri Belli Oldu

Mafia 3 Sistem Gereksinimleri Belli Oldu

Meraklıları tarafından bir süredir beklenen yeni Mafia oyunu, birkaç ay önce duyurulmuş ve ardından yanlış fiyatla ön siparişe çıktığı için Steam Türkiye’den kaldırılmıştı.

Son olarak geçtiğimiz hafta oyunun geçtiği şehrin bir dakikalık kısa videosu da yayınlanmıştı. Mafia 3’ün sistem gereksinimleri de açıklandı. Oyunun 7 Ekim’de PC, PlayStation 4 ve Xbox One için çıkacak.

Mafia 3…

View On WordPress