Видео

Basic source where I started learnopengl.com/Introduction that's also including assimp animation. For postprocessing and to get some inspiration : www.shadertoy.com/ and forums like gamedev.net/forums/ and forums.tigsource.com/index.php

@@MrEscen Thanks

Thanks...It's the journey that counts for me, at the same time I want to create general useful features for my engine. It's a slow progress in spare time. Why my own engine? That's work related, understanding how 3D graphics works helps me a lot, even if it's not my part of profession.. But stay tuned I have many ideas to work out.

thanks...where is the fun if it was easy😏

🎊🎄

Hello... yes Qt based editor. Editor and engine are separated executables with an udp socket for communication, so the engine can run 'standalone'.

No never tried ANGLE

Thanks

ow damn it was openGL itselft HAHAHA ngl this looks cool

Thanks... It's not my profession but certainly fun to do. For any tips, take some time to look into different way of rendering. I'm using deferred rendering combined with many postprocesses, but it has its disadvantages. I think it's worth looking into your pipeline before starting. Depends of course if you want to make a game only or a render engine. Edit: another tip: learn advanced shaders, if you master compute shaders great things happens.

Sorry to disappoint you but my code is not the best example out there. It needs a real cleanup and that will take a long time. Over the years I made too many test cases. It's like a sandbox with spaghetti. I think on github their better and smaller engines to learn from. Maybe you can put the fee in an online course.

Prusa has a nice G-code viewer. 100 times better. This was just a test to tryout Qt3Dwindow (never going to use it again... so successful test :)) and to test a line shader. In Prusa on 'plater tab / 3d view' just click on the bottom slider and a textwindow will popup.

The terrain is just a heightmap. I do have a node based terrain generator in this editor (never showed) but in this case I'm using a real part of France heightmap :). The trees and foliage are procedurally generated. Each rock, treetype or foliage has it's own instance layer with different level of details (LOD's). For each layer, placing is done with a compute shader. A fixed grid buffer is sent to the compute shader where I can move, ignore or add grid positions...for example with the same heightmap I can calculate terrain slope and move rocks along that slope. This grid buffer is send back to the the instance shader and draws a layer mesh on every new position... Nice thing is when I load another heightmap everything is different... takes me hours to just walk around and see what happened. That is the fun part I guess... and was my goal.

@@MrEscen super cool! I love your procedurally generated vegetation! I hope i will be able to do something similar someday. Keep up the amazing work!

​@@3DProgramming Well you're getting close achieving that. I'm still having some popping issues and build way to many postprocesses that slowly screw up my colors... but it can be solved, just need some time... doing great yourself!

@@MrEscen thank you! It is a great compliment when it comes from someone as you. I still have a lot of work in my engine, my engine still lacks a lot of basic and more advanced features, and I admire especially your amazing LOD system, I suppose there is a lot of work behind it. Have a great day and keep up your amazing stuff!

Yes I'm using QtWidgets for my GUI but did it a bit different. Wanted to have my engine and editor separated. In that case I could run the engine without any Qt dependencies. The editor and engine are two separate executables. The editor catch the engine SDL window handle (HWND). Communication is done with a UDP socket. Configurations and project files are stored with lua scripting. Done that years ago, works without problems.

@@MrEscen Very interesting, I've thought about separating things that way as well, but never really went forward with it. I keep my engine/tooling completely separate as well and expose some extensible platform code. My tooling extends using Qt functionality and games would just handle things with SDL directly. In fact, I don't even require SDL in the engine, I could build it with just Vulkan/OpenGL libs.

@@NickEnchev Included SDL at that time because it has easy access to game controllers and joysticks.

@@MrEscen Yeah no doubt, SDL is great.

@@Xandor70 Heb je die frisse buitenlucht wel eens geroken.. Bah. Radar zit er al langer in.. het is een postprocess, hij stond nooit eerder aan. Grappig om objecten met radar proberen te vinden.

This is my own opengl-engine, using Qt for interface.

@@MrEscen sorry I ment text editor😅

@@CDev12 for text editor I'm using Notepad++, mostly for editing shaders and lua scripts. But if you talking about an IDE.. Visual Studio and CodeBlocks.

you're right...more blue-ish, that's easily done, it's already running in a post process, thanks.

Oh thanks, I was aiming for a space simulator.

Thanks.. You're doing great yourself!

@@MrEscen thank you! I'm glad that you think so :)

Yes this is my own engine. I'm trying to make a full game editor out if it... Recently I implemented an event system for animations. Maybe I show it some day... But just like those SDF insects it's a new render method to learn. It's a post process with endless possibilities. Just used to fake some falling leaves. Check it out on www.shadertoy.com/view/M3sXWB But many other subjects to learn. Just for the fun of it.

@@MrEscen This is beautiful. I'm amazed by what you made. I'm still stuck with 2D in OpenGL. Still haven't made the transition to 3D, but I do want to. Implementing lights and all that, skeleton animations, etc. Must be super, super complex I assume?

@@luigiistratescu2756 One reason I started my own engine is that I didn't want to lose all my previous work. Every new idea or techniek I put in my engine. Some will stay, some don't. Skeletal animation done that years ago.. (still have to finish animation blending). Physics is still there, path finding, ect. Before that I was working on many separate projects, that was time consuming. Now I already have a class available and implementing goes easier. There is of course some planning ahead before I start coding. There are some good code examples out there for animation learnopengl.com/Guest-Articles/2020/Skeletal-Animation . Maybe you should also take a look at deferred rendering very nice for lighting but also useful for many post processing effects because you're able to store world-position per pixel.

@@MrEscen Impressive! I am building my own, I got some UI working with ImGUI, I got Phong Lighting working, all I'm trying to do now is wrap my head around Assimp. But I just get super frustrated. Everytime I load a model it's buggy, it's distorted. Honestly, building my own engine has been the hardest endeavour of my life. When I look at what you've build, I'm just impressed.. I have a very simple thing in mind. I'm a Blender user, I know how to model, I used to make animations, etc. All I want is an engine in which I can upload models (that I make and animate) and start building my game. I want to make a game similar to Trine 2, but better. The assets, I have them, and I continue making them. But it's this stupid technicality... loading models.... so hard! :(

@@luigiistratescu2756 Well it will depends on what you really want to achieve. It's a well known dilemma. If your only goal is making a game it's better to use a game engine. Shadows are enabled just by a simple checkbox. Making a game engine is not easy. It took me several attempts to get the right shadow system working for my engine with a lot of errors. My goal is to understand how render engines work. It's the journey that counts. I'm an engineer and it helps me a lot understanding the industries I'm working in. Of course you can do it all, modeling, game engines and creating your own. Consider the goal where to put the time.

Editor and engine are two separated executables. Editor catch the 'window handle' (HWND) using Qt for UI.

Sorry no... This was a test with Qt3Dwindow, had a lot weird window issues on different displays and even crashes when camera moving to many times. Very hard to find or no info on using advanced interface shading and had to get back to direct using OpenGl ( and it's not possible to draw over the graphicviewer)... not a good base to continue :( ....So it was a successful test

Thank you! Cheers!

Als je heel snel bent loop je nu naar buiten.... kan je nog even in de sneeuw lopen :)

Editor and engine are two separated executables. Editor catch the 'window handle' (HWND) and starts/stops the engine. Communication is done with an UDP socket. Engine compiling is done in a regular IDE. Made this setup years ago and it works without problems. Projects and configurations are stored in simple text files and/or using Lua scripts.

@@MrEscen sounds very interesting and not how I expected this to be done, thanks for the explanation!

Well I'm learning myself. Wouldn't listen to my own instructions.... But how I handle the technical part and workflow of the terrain is something Interesting. Maybe that's something I would like to share and worth a tutorial. Don't pin me on it.

@@MrEscen I'm very impressed. Some of my life goals are being achieved on this channel, to make an engine and a game as a long term hobby. What are your sources for learning. I used thin matrix, victor gordon and learnopengl. So far I have bullet physics, terrain, reflections and lighting, and workingn on framebuffers now (Water) any goto places for water help?

@@AlbertRyanstein One of my goals was to have a walkable terrain. So no difference there. ThinMatrix has a good tutorial on water, but sometime I search on github to get some examples to learn. I do contribute on github but mosly on other topics. Another resource is Shadertoy, good for calculations and inspiration. It's all done in screen-space good for postprocesses. I suggest looking into deferred rendering. It comes with some drawbacks but you can render in multiple framebuffers that can be used all over your engine (object-picking, processID's, pixel worldpositions, postprocessing, ect). Very handy is to understand matrices /quaternions translation and rotations. The use cases of quadtrees also really helped me out. We are on the same journey if you have any more question just let my know. learnopengl.com/Advanced-Lighting/Deferred-Shading www.shadertoy.com/

Bob kwam maar met 1 skeleton animatie, en dat was hardlopen... dus hij heeft geen keuze

@@MrEscen hardlopend zie je wel meer in kortere tijd. Bob houd het tempo erin.

Well it is an interesting journey... but don't use a crappy pc like I did for years, finally replaced that thing 😊

Cascade shadow mapping / deferred rendering. Adapted version but probably based on learnopengl.com/Guest-Articles/2021/CSM

@@MrEscen thanks 😊

Thanks, I will do that, fog needs some more work, looks weird indeed. I was focused on performance..

Hello @lasttrump6015... Well most admit, after 11 years I don't remember how it was done. I was using Irrlicht in that period. Nowadays I would do it with deferred rendering and some glsl post processing.