• 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.


  • Content count

  • Joined

  • Last visited

Community Reputation

144 Neutral

About Lunatix

  • Rank

Personal Information

  1. Umm.. okay, this wasn't clear enough >_< I don't use any function of opengl, theese are my own functions, but i'd like to get them work as OpenGL 1.1 supported them.. it was more the question, if i'm right or wrong with my thoughts..
  2. Hi! Currently, i'm writing a little raytracing library, everything worked very well - but now, i'm implementing matrices for the transformation.. so i would like to make some things right, because i think they could be wrong: - LoadMatrix: Simply resets all Push and Pop stages and loads the given values into CurrentMatrix. - PushMatrix: Creates a new matrix, copyies the current stage and pushes the current matrix on stack - MultMatrix: Multiplies CurrentMatrix * ObjectMatrix - PopMatrix: Restores the last pushed stage - Normal Matrix: Upper 3x3 of CurrentMatrix, Inversed, Transposed (Compute it every time Load or MultMatrix is called) - Set a Vertex: Vector(x, y, z) is multiplied by CurrentMatrix - Set a Normal: Normal(nx, ny, nz) is Multiplied by CurrentMatrix -- or, when computed by intersection algorythm, this normal is used (and not transformed by NormalMatrix?) - The Lights: Position and Direction is recomputed each "LoadMatrix" is called, not multiplied by CurrentMatrix - Rays of Projection: Computed once per "SetViewport" - because our world is transformed, it isn't necessary to transform them Would be nice if someone knows, if my thoughts are right or not.. Happy coding, Lunatix
  3. Hey! Thank you Ravyne, these informations are very good [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img] I will keep this in my mind, if i start with OpenCL. And finally, i have managed to get my new library to work, and now, its about 10 times faster as before [img]http://public.gamedev.net//public/style_emoticons/default/smile.png[/img] If someones interested, read more at our (LunaGameWorx) Blog site in the Raytracing section: [url="http://gameworx.org/index.php/raytracing-articles/"]http://gameworx.org/...acing-articles/[/url] But i think, 740ms per frame is even slow, if i see something like this -> [url="http://dinkla.net/de/programming/cpp-parallel.html"]http://dinkla.net/de...p-parallel.html[/url] In the Videos, if the application starts up, they are using only one thread for computing and git 8 Frames per secound! Once again, 10 times faster than mine.. are there some tricks to speed up calculations or function calls in c++ ? And, should i use float or double vectors? My vector struct has double's, because i thought, vectors should have good precision in a raytracer or rasterizer.. Edit: I switched to Release and /Os -> Now i have only 103ms per Frame and ~9Fps ! Awesome =D Maybe, i should write a bit more inline asm code in my vectors Oo Edit2: Found the SIMD SSE2 Switch, now i'm at 13fps and 71ms per Frame!
  4. samoth: In some cases, you're right - i shouldn't worry about it. But in my case, i want to get experience! I don't even want to look up at those people, who writes librarys like OpenGL or DirectX and think "Theese people must be some kind of gods *_* - no, i want to be one of those people, who know the mechanics behind the scene - just a little bit! By the way, i got it working. I searched and found, my solution uses CreateDIBSection and BitBlt and other of those basic GDI functions. And, i think, it works good. After programming this i found an equally method in the SDL Source code And now, i can call "wrtCreateContext(MyPanel.Handle);" from C# and my library does all the steps necessary to create a GdiPixelBuffer and a rtContext for drawing
  5. When i got the raytracing working again, i will modify my raytracing code a bit and use OpenCL for computing. The thing was, that i had my own "Pixmap" which the final colors where drawn to - and i had to copy this colors (public struct RTColor) to the Bitmap via "MyBitmap.SetPixel(System.Drawing.Color, ..)". This took to long, and i don't wanted to write unsafe code, because i think, if i'm programming in a managed enviroment, one should not use unsafe code until no other solution is left. So this point and the fact, that i had to do unsafe calls to get OpenCL to work with c# and the speed improvement of a c++ language lead me to this solution - to rewrite the Raytracers Core in c++. And i don't think, C# is very good for such a type of project - because managing all those vectors, colors and rays by the GC is a (for me) to heavy performance lack (leak? lack?). And my core is finished, and my first (because simpler) solution was a rtContext which has an abstract rtPixelBuffer class which it will output the final pixels. So, in C#, i call "wrtCreateContext(HDC DeviceContext)" via DllImports which creates a "GdiPixelBuffer" and the result is a valid rtContext with a rtPixelBuffer (GdiPixelBuffer)..
  6. Very funny, powly K ;) I don't wanted those kind of "direct" access, it was more a question, how OpenGL or DirectX brings the final pixels on the window, just to understand this technique. I tried something like: creating a panel and setting a bitmap as background image, then write to that image - this operation costs ~400ms (C#, my first raytracing approach was written in this, but now, i ported the code in C++ as a library for more speed). And because of this lack of performance, i thought i could get a bit more "direct" access..
  7. Thank you This is a good approach / hint! Now, i cann turn on google with a more specific "knowledge" of my problem ;) Think i will get this working.. because i'd like to get "direct" access to a buffer, without calling gdi or using bitmaps for my raytracer.. such a "step in the middle" costs to much time. Thanks
  8. Hello! I would like to know, how a graphics api like opengl finally draws to a window's handle.. i know what a pixelformatdescriptor or a HDC is, but my question is - how draws opengl the final "pixels" to the control / handle, whatever? I downloaded the Mesa GL source code and i'm trying to find something.. but maybe, someone knows a sample or something or another solution for my problem?
  9. You're right, i see it too =D Maybe something interesting, here's an article about animated clouds via perlin noise.. sounds interresting o_o [url="http://freespace.virgin.net/hugo.elias/models/m_clouds.htm"]http://freespace.virgin.net/hugo.elias/models/m_clouds.htm[/url]
  10. Okay, thank you guys for your approaches I think, that i will use the two quads with cloud textures... i thought it could be something more *magical* ;)
  11. From the album Luna Game Worx

    © LunaGamwWorx, Denis Germ aka Lunatix

  12. From the album Luna Game Worx

    © LunaGamwWorx, Denis Germ aka Lunatix

  13. From the album Luna Game Worx

    © LunaGamwWorx, Denis Germ aka Lunatix

  14. From the album Luna Game Worx

    © LunaGamwWorx, Denis Germ aka Lunatix

  15. I've wirtten an own (voxel) terrain renderer, so i can say, the first thing what differs from your renderer is, that minecraft's blocks 3 times bigger than yours. The secound thing is - for such big geometrical structures - use vertex buffer objects and calculate your geometry only once per change. Also play with the sizes - 32x128x32 is a good size. And be shure, that you only hold chunks in a viewrange + precache range in memory. (If you are interrested in pics, click here [url="https://www.facebook.com/pages/Luna-Game-Worx/286480244750104"]https://www.facebook.com/pages/Luna-Game-Worx/286480244750104[/url] ;)