No one uses raw directx anymore?

Started by
7 comments, last by Hodgman 11 years, 3 months ago
I've been trying for days to find a person with directx knowledge,but it's impossible! Everyone is using unity these days or udk,or cryengine.

Is there anyone left that uses just directx?
Advertisement

You should probably ask in the DirectX subforum wink.png

I've been trying for days to find a person with directx knowledge,but it's impossible! Everyone is using unity these days or udk,or cryengine.

Is there anyone left that uses just directx?
Not true at all, on my comp theres at least 6 books on directx which keep getting updated and 4 on HLSL or shaders in general, theres also 2 on COM but they arent really needed for directx, more for understand COM itself

Frank Luna's book will get you through the basics, after that its GPU gems, theres nothing special with directx that needs a lot of books, after a while you realise it becomes more about maths than anything

EDIT: I just realised you said person not books, my bad hahaha, yeh check the DX sub forums ;)
I've been trying for days to find a person with directx knowledge,but it's impossible! Everyone is using unity these days or udk,or cryengine.

Is there anyone left that uses just directx?

weird, their might be some sub-forum, might have the name directX. might have some people that know things about directX. idk, maybe it's just my imaginary friends telling me lies again.

Check out https://www.facebook.com/LiquidGames for some great games made by me on the Playstation Mobile market.
I've been trying for days to find a person with directx knowledge,but it's impossible! Everyone is using unity these days or udk,or cryengine.

Is there anyone left that uses just directx?

Most hobby projects will use these because it's a lot easier to use something like unity when you simply want to make a game quickly and efficiently, lets face it without extensive knowledge through reading up on efficient design (and remember to actually write a game rather than focusing on making an engine as per the famous article by jpetrie write games, not engines) and other such things you will very unlikely produce anything that compares to stuff that is already made for you. They also typically provide a way to work on one thing and have it (relatively easily) transfer onto multiple platforms which is an important feature when trying to get as much coverage as you can with your game, while writing native C++ in DirectX will of course not (fairly obviously).

yes but I mean...If you wanna work for a big company what are you gonna say? I know how to script,but directx beats me?
yes but I mean...If you wanna work for a big company what are you gonna say? I know how to script,but directx beats me?

In big companies, not everyone deals with the graphics code.

For example, a gameplay programmer would benefit from scripting knowledge, but graphics programming wouldn't greatly benefit this role.

Saving the world, one semi-colon at a time.

yes but I mean...If you wanna work for a big company what are you gonna say? I know how to script,but directx beats me?

Well me personally I've done brief work in DirectX 9.0c in my own time about 3 or 4 years ago, plus as part of my computer science degree I'm currently on I'll be using OpenGL next academic year.

It's useful to know how to use them but chances are you wont be going straight into graphical programming fresh out of university unless you did a degree in mathematics and joined someone like Nvidia. As I said though hobby projects are almost always best of using something that does a lot of the work for you, and in most jobs you will be working with some form of middleware (even if some of it is developed in house).

yes but I mean...If you wanna work for a big company what are you gonna say? I know how to script,but directx beats me?

At my last job, I was a "graphics programmer" in the game-engine team, which meant I was pretty much the only guy who used DirectX directly.

It's nice for all game programmers to know how graphics work at the D3D/GL level, but it's only really required if you want to specialize as a graphics programmer.

Also, at the job before that one, I was also a graphics programmer (but this time directly attached to a game team, instead of the game-engine team), and I never touched D3D directly - I always used our engine's wrapper around D3D/etc...

This topic is closed to new replies.

Advertisement