• 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
Paul C Skertich

Should I do DX GUI for Level Editor GUI?

7 posts in this topic

I am still very excited about my level editor in Win32 API in C++. I fully initialized DX when I click on File -> New Scene. I was in my mist of creating a edit bar (simple Dialog Box) where I noticed once I initialized the DX11 Device and moved the dialog around - it left nasty crap behind. For instance, the blue DirectX display when back to the original background of the Windows program. The Win32 Modless Dialogbox is a child of the main window.

I'm asking if I should chose a MDI Form or use a DirectX GUI? Should I reduce the view port size of the DirectX like in half then the modeless dialog wouldn't get in the way? What is the best approch should I handle this? Thanks!
0

Share this post


Link to post
Share on other sites
Historically mixing GUI and accelerated rendering has been somewhat troublesome at the very least.
It was my understanding post-areo would make them work. Bad to know I was wrong.
Personally I would suggest dropping OS GUI frameworks. DXUTGUI (I don't know if it was ported to D3D1x) is good looking but a bit of a quick hack, I suggest to stay away from it.
I've been looking at CEGUI for quite a while but greatly misunderstood the documentation for a long time. The author himself chimed in a few days ago and somehow I got the illumination I couldn't see for so long time. I strongly suggest to have a look at CEGUI.
0

Share this post


Link to post
Share on other sites
ouch, using Win32 for a level editor? You like pain I guess.
If you are doing this as a learning process then it's all good. If you need to get something working I strongly suggest you to rethink the approach :)
Best options would be QT and Borland Builder series if you want to stay C++, or C# WinForms + Managed C++ interface to the engine side.

I use the second approach for my editors and I don't have to curse the world and write 100 lines of code if I need to add a button :)

"Gamey" gui system such as CEGUI or DXUTGUI are ok to use in the game itself because you don't have a choice, but in an Editor? You have a choice, don't hurt yourself :)
1

Share this post


Link to post
Share on other sites
I think your life would be easier if you export ur core code into dll and make the GUI in C#.
I'm not fan of microsoft but I think this gonna be easier.
0

Share this post


Link to post
Share on other sites
Kunos, no wonder why I keep on thinking to myself, "This is absolutely crazy! There has to be a better way!" I'll take your idea! Thanks everyone for their support! Whew, no wonder why my head hurts - the brick wall DOES HURT! :D
1

Share this post


Link to post
Share on other sites
Kunos, so, I started to make the pretty interface in C# then I plan to bring in the managed game engine functions - is this possible? Also what about a user form control to have directx functions, for the level editor would this be even better?

I just woke up, so may not make a lot of sense right now! LOL!
0

Share this post


Link to post
Share on other sites
If your engine is already done in C++ you have 2 options:

- You can expose your engine through a plain C interface, then call those directly from C# land. This is a good exercise and it'll give you the possibility to expose the engine to Mono as well pretty much every other language that can bind with C.
- You can expose your engine using a Managed C++ dll .. which is what I do.

None of these have particular pro/cons

If your engine is not done yet.. then you're still in time to see the light and do everything in C# using SlimDX to interact with DX11. SlimDX (or the alternative SharpDX) is a almost 1:1 .NET binding for the entire DirectX world.. you can easily translate from any tutorial you find in C++ in C# in minutes, functions names, objects and parameters are the same.
1

Share this post


Link to post
Share on other sites
Kunos, you're awesome for helping out amongst others too! Thanks for clearing up some gook out of my head! Much appreciated!
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