Відео

I really wish to understand these things a bit better. I have programmed in so many different things and my knowledge about openGL is not much more than when I left University as I've never used it for anything but personal experiments. I really would like to understand it better tho. I am also a big fan.of shaders, but it's something I have picked up a few times, but also have not look up too deep into it.

What are you using to edit? I know a bunch of folk who use Da Vinci Resolve and swear by it.

I have never heard of Nsight before. That seems like a useful tool. Although in my case I haven't needed it so far. But it is good to know that it exists. When it comes to video editing I just bought the microphone Shure PGA27 which a sound technician recommended to me, I have a nice mic stand and I use DaVinci Resolve. I have a pretty bad ear when it comes to noisy, poppy or distorted audio. So I just went with something that is sure to work and ignored it from then on.

See system microphone settings. Pay attention to two settings : - sampling frequency, the best setting should be the value you use in the video (it will probably be 44.1 kHz, but Windows has a default setting of 48 KHz - this may be the first cause of the problem). - make sure that you do not have "increasing microphone performance" enabled, very large values of this parameter will overdrive the value and there will be crackling noises. From the audio editing side - in the editing program, select whether fragments should always be cut at the zero crossing point, or select the transition between fragments to be gradual. - Some programs have the function of catching crackles and noise and reducing it. You can try the "DaVinci Resolve" program. If the crackling occurs only when speaking, wear a cloth at some distance from the microphone.

So, now I'm subscribed to you with my correct UA-cam channel. I like those brush implementations. Could you make a video with your game idea? It sounds like you have ambitious plans.

Does biweekly mean twice a week or every two weeks. :D

5:00 Instead of message just hook yourself to keyboard and don't allow anyone else to grab keystrokes? Keyboard Hook Example, HHOOK llkbdhhook; LRESULT LowLevelKeyboardProc(INT nCode, WPARAM wParam, LPARAM lParam) { if (nCode!=HC_ACTION) {return CallNextHookEx(llkbdhhook,nCode,wParam,lParam); } //Here you put your stuff register BOOL fProcHandled; // helper variable, keyboard was handled register KBDLLHOOKSTRUCT *pkbdllhook = (KBDLLHOOKSTRUCT*)lParam; // Ctrl, Alt, Tab, activate Tab if Ctrl+Alt was pressed, don't clear Ctr, Alt state, other keys clears that state if (wParam==WM_KEYDOWN) { switch (pkbdllhook->vkCode) { case VK_LCONTROL: // CONTROL triggered down event KeyPressed.Ctrl =true; goto KBRETURN; break; case VK_LMENU: // ALT triggered down event KeyPressed.Alt =true; goto KBRETURN; case VK_TAB: // TAB trigger down KeyPressed.Tab = true; if (KeyPressed.Alt==true && KeyPressed.Ctrl==true) goto CTALTTAB; else goto KBRETURN; // allow other programs handle that key whatever it was default: if (KeyPressed.Alt==true && KeyPressed.Ctrl==true) goto SHORTCUT; // if Ctr + Alt was pressed handle shortcuts else goto KBRETURN; // if not just allow other programs handle that break; }} else { // Ctrl, Alt lub Tab i KEY UP UP UP UP RELEASED, clear variables and allow others to handle keyaboard if (wParam==WM_KEYUP) switch (pkbdllhook->vkCode) { case VK_LCONTROL: // CTRL KeyPressed.Ctrl=false; if (KeyPressed.Locked==true) goto CTALTTAB; else goto KBRETURN; case VK_LMENU: // ALT KeyPressed.Alt =false; if (KeyPressed.Locked==true) goto CTALTTAB; else goto KBRETURN; }} //------------------------------------ KBRETURN: //allow others to read that, unhandled return CallNextHookEx(llkbdhhook,nCode,wParam,lParam); //------------------------------------ CTALTTAB: // CTRL ALT TAB CASE handled by some function within program, don't clear CTRL+ALT, allow TAB to be sequencially pressed, and trigger calling for some function each and every time fProcHandled = WindowSwitcherProc(pkbdllhook->vkCode,wParam); if (fProcHandled) { return true; // if handled return true } else CallNextHookEx(llkbdhhook,nCode,wParam,lParam); // if not allow other programs to handle that //------------------------------------ SHORTCUT: // CTRL ALT + ANY OTHER KEY clear the CTRL ALT once it's handled fProcHandled = ShortcutProc(pkbdllhook->vkCode,wParam); if (fProcHandled){ KeyPressed.Ctrl== false; KeyPressed.Alt = false; // clear the global variables, return, true handled return true; } else CallNextHookEx(llkbdhhook,nCode,wParam,lParam); // unhandled allow other programs to handle return false; default return, of this callback wasnt handled } //--------------------------------------------------------------------------- ///Helper for callback, define shortcuts pressed once, require CTR+ALT to be pushed again, if handled, contrary to section where Tab was handled that one allowed multiple strokes while user kept CTR+ALT pressed down, there two types of "helpers" here. LRESULT ShortcutProc(INT aCode, INT aEdge) { //------------------------------------ static DWORD last_time = time(NULL); static DWORD current_time; //------------------------------------ current_time = time(NULL); if (current_time - last_time > 60 * 100) { // you can filter out multiple key presses too fast, } //------------------------------------ // Here define what each key press do, allow if Alt, Ctrl was pressed not released, while your windo was active, your windo was first in hook chain switch (aCode) { //------------------------------------ case VK_END: // kill application on top //------------------------------------ if (Desktop->Action(KILL_PROCESS,GetForegroundWindow(),0,0)) Tips_form->Execute("PANEL->Process: KILLED!",true,false); return true; //------------------------------------ case VK_F1: // show help window case '1': // 1 case 'X': // X CTR + ALT + X } return 0; // ZERO FALSE to ALLOW other programs handle Or return true to confirm key being handled } // Initialize all stuff WINMAIN WINAPI WinMain(HINSTANCE, HINSTANCE, LPSTR, int) { HANDLE hMutex = ::CreateMutex(NULL,TRUE,"sstsoft::mutex::Panel.VCL"); if (GetLastError()==ERROR_ALREADY_EXISTS) {return MessageBox(0,"Running multiple copies is not allowed", "YOur appli cation", MB_OK|MB_ICONERROR|MB_SYSTEMMODAL); } //------------------------------------ KeyPressed.Ctrl = KeyPressed.Alt = KeyPressed.Locked = false; // Hook activated! llkbdhhook = SetWindowsHookEx(WH_KEYBOARD_LL,(HOOKPROC)LowLevelKeyboardProc,(HINSTANCE)HInstance, 0); // mousehook = SetWindowsHookEx(WH_MOUSE,(HOOKPROC)MouseProc, (HINSTANCE)HInstance, 0); // cwphook = SetWindowsHookEx(WH_CALLWNDPROC,(HOOKPROC)CallWindowProc, (HINSTANCE)HInstance, 0); // file hook is also possible don't have example, never tested, WaitForMultipleObjects is better anyway so.. //do whatever you want /// cleanup UnhookWindowsHookEx(llkbdhhook); CloseHandle(hMutex); }

Which features are you most excited / most ambitious in implementing for your engine in the far future?

The discord invite in the description has expired :b

Early keyboards had three functions per key; lower case, upper case and ALT. Newer keyboards moved these Alt functions to the function bar, F1 to F 12, the special keys and the number pad. So the Alt coding is still set to wait for those functions even though we have new keys for them. Most game code just overrides it but your starting from scratch.

This looks fantastic!

just do a relaxing 15min video about building a giant castle next time. it's so satisfying to watch :D also will you ever do other meshes than whole voxels? and will you ever randomize face normals a bit for extra detail?

I see these ::, i know the language you've written it in.

could you explain a bit more on how the lattice coordinates work in relation to the voxel coordinates?

This is really cool! What's the performance like right now, in regards to things like several random edits to the voxel data, sequential edits to the data, etc?

I’m just pleased this is open source. There are great voxel engines on UA-cam however most of them are not open source - so not useful. You’ve got a new subscriber.

Back when mouses weren't common the Alt key was used to switched focus to the menu and back (still does for most applications), which I'd guess is where the VK_MENU keycode comes from. Also the menu shortcuts used Alt + some character from the menu command (marked with & in front in the command name, which Windows automagically underlines and uses for the shortcut) eg. Alt + S for &Save, which I'd guess is the reason for the WM_SYSKEYDOWN/UP messages. Depending on how you're creating the window you should be able to disable the system menu eg. if you're using WS_OVERLAPPEDWINDOW that includes WS_SYSMENU.

Looks fantastic!

which language i need ? to use your voxel engine. It's great

This looks so cool! The surface brush can make some nice ruins. Btw, maybe a long shot, but your code style kinda reminds me of handmade hero. Have you done that by any chance?

It's looking great so far!

that seems pretty damn cool ! can't wait to see where it goes

When it comes to being backwards compatible with your data files you *can't* go wrong looking at how Blender does it. Similarly to what you described, it saves a descriptor of what fields goes in which offset. Then it just stores the data right from memory to disk, and maps which memory address maps to which file offset. Afterwards, you can just parse the descriptor, deal with any missing data caused by new features, and correct the pointers. Oh, and correct endianness if necessary. They "recently" made some breaking changes, but prior to that you could still open a file saved in the first alpha version in the latest version. It cares a bit more about being fast at saving though, since you do that a lot more than you load your work. If you want to make loading faster some of the work could be done on save instead.

I really admire your speaking skills! That's something I struggle with a lot.

Nice. The white noise brush would be more useful with a density slider (noise threshold) and maybe an option to "blur" by introducing a Guassian to the noise threshold.

I remember when I first started using linux as my main os, my middle mouse button didn't work. I tried changing everything in the os to make it work, it ended up being the mouse itself 😅

Starting to look real good :)

Your brush system looks really nice

🎉💜🤍💜🤍💜🤍

I like how the noise is global, different structures connect in a pretty way

I dont expect a tutorial or anything but do you think youll go into technical details with these devlogs? Looks pretty promising!

This is the... sixth? eighth? novel voxel engine devlog channel youtube has pushed on me in the last 30 days 😂 Keep up the amazing work! subscribed and notified! 💜🤍💜🤍💜🤍

YES! Good stuff!

wow!

for a second I read it as "Bisexual voxel engine"

This looks really cool Ill be happy to follow this (But please fix the mic popping T-T)

This is so coool :)

Great video! Subscribed.

3:45 Man I almost did something like this myself, it's a shame that it's so difficult to do this

I think you copied your previous description, because the link to the GitHub repo doesn't actually work.

The GitHub Link to the latest version is cut off ^^

void* extravaganza

The engine is looking great!

Dude too much fog! :D But really really cool engine!

Very pretty, nice work!