• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
gasto

DirectInput's awkward and inconsistent terminology.

4 posts in this topic

In the first paragraphs of the introduction to DirectInput by Microsoft:
 

Device object
Code representing a key, button, trigger, and so on found on a DirectInput device object. Also called device object instance.


Yet, everywhere around the site one finds references to device objects as if they were DirectInput devices(keyboards, mice, joypads, joysticks, etc.) For example in the EnumDevices method explanation:
 

dwDevType
Device type filter.
To restrict the enumeration to a particular type of device, set this parameter to a DI8DEVTYPE_* value. See DIDEVICEINSTANCE.

Edited by gasto
0

Share this post


Link to post
Share on other sites

"Device object" on that page looks like a typo for "Device constant". I don't think the API is that awkward compared to anything else from Microsoft, though apparently the documentation could use some editing, which also isn't that unusual for Microsoft.

1

Share this post


Link to post
Share on other sites

I mentioned this in another post, but you shouldn't use DirectInput as stated here : http://msdn.microsoft.com/en-us/library/windows/desktop/ee416842%28v=vs.85%29.aspx

 

"The use of DirectInput for keyboard and mouse input is not recommended. You should use Windows messages instead."

 

You can also use raw-input.

 

Per the OP's previous posts he appears to be using it for joysticks.

1

Share this post


Link to post
Share on other sites
Yes, Direct Input for joysticks and Windows messages for traditional keyboard and mouse. However if I want to cover Xbox 360 controllers I must use Xinput as well.

I think that all three of them support immediate events and buffered input.

I recently played a Tiny Brains demo on Stream and it seemed to possess no support for DirecInput because the y axis on the left joystick(or so reported in the driver's utility) was inverted, and the right joystick seemed to partially work only for the left hemisphere of rotation, which makes me think that Xinput misrepresents classic USB controllers.
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0