reepblue

With C++ I tried disabling occlusion culling for the collapse brushes and it didn't do anything. For lights I'm thinking adding Draw hook functions for every point light that has a radius greater than 5. It'll check if the camera's position is in it's AABB and temporarily disable OC mode if the point intersects and re-enable it if the camera is out of it's bounds. I'll have to see if it's worth it. You're playing with fire when it comes to this stuff this is why Josh recommends you just leave everything as default.

While it does fix this dreaded issue, I'm noticing a performance penalty in debug mode. I have it as a console variable and I'll continue to experiment with it. I didn't really care about the brushes as much as I did with the point lights. I think setting this to false on the camera is just omitting all OC functionality which is causing the application to run slower.

I recall you being on a 1050ti and I also use that card for my development machine and I think it only has 2GB if VRAM. Yeah, a better card means it can do more things at once, but if your game is capped at 60hz, other engine is only going to go that fast. Due to how the renderer is set up, things will cull based on the speed of the app. Again, I would just set vsync off by default and put a higher frame rate as the second parameter in your sync call so the game will not fluctuate in speed too much. If you do 120fps and the game goes to 90fps; you'll barely notice it compared to 300 to 90.

View this video Description I pretty much took my base player code and added a ton of functionality such as soundscapes, HUD features, Input Glyphs, and more.

I rolled back to my previous solution for many reasons. I would have to check the entity's normal and swap out what scale values to use. I have to create a spawner class anyway which does a calculation to determine the base size from the texture. I would not be able to see the results in the editor anyway. My overlay classes are never intended to resize during runtime. The information was helpful and I hope it's useful to others!

Thanks for the start. The compiler complains about the len() function, so I replaced it with length. I'm getting the desired results with decals, but not with planes despite it using the same code. If I could remove the normal blending with the decals, I wouldn't be making an overlay class.

Is there a way to get the entity's scale value based on the matrix value? I'm currently passing scale modifiers via code but I'd like to see the results in the editor if possible. How would I do this? Examples would be the most helpful!

Tbh, I fund the culling of lights to be more annoying especially if you are using point lights to light entire rooms.

Right. This is why I suggest making entire rooms models if you can. The entire room will not get culled because you'll be always looking at it.

You can pretty much use whatever you want if you can grab the window handle like seen here. If something doesn't work, you can let Josh know here.

The brush culling is less noticeable with a black clear buffer (This is set up as the default) with the frame rate above 90. Your CSG gets collapsed into multiple models, but in most cases half of your one room will be it's own slice. There hasn't been any clarification how the engine determines how to cut up the CSG. Another option is to model your indoor level into sections so you can control how your indoor levels cull. This is a big pain since the main reason I switched to Leadwerks was due to it's editor and the obj export doesn't export the uvs. I haven't found any blender plugins that mimics the texturing features like in Leadwerks. I would not worry about it until your art pass in which you would be in a better place to mesh your level off the CSG if it really bothers you that much. My game however needs the collapsed CSG for the mechanics to work.

Most people are still using intel Macs anyway. Hopefully that bug will be fixed in the future. Upside is that at least you know the code will compile.

This is the occlusion culling working and the renderer not keeping up. I've fought with this for my years and figured out that disabling vsync by default and capping the framerate above 100fps reduces the effect a lot. This will keep the app at a consistent rate while reducing the culling effects I use 120hz as my target framerate. context:Sync(false, 120)

Put it on the backburner for now. I'm sure this will be fixed eventually.

Are you putting it in the right directory? Desktop files: putting your application in the desktop menus (gnome.org)

Nice work. Yeah, XCode is a pain with output directories. Let us know what you find.

This is the more important bit. Really cool!

Did you try this? Seems the only error is with LSEEK. The rest is Clang being annoying. #define _LARGEFILE64_SOURCE /* See feature_test_macros(7) */ #include <sys/types.h> #include <unistd.h> android - implicit declaration of function 'lseek64' is invalid in C99 - Stack Overflow There is a similar issue with this repo, maybe the solution is the same? Install failure on macOS 11.0.1 Homebrew python 3.9 on Intel Hardware · Issue #828 · PyTables/PyTables · GitHub

Neat. I'm actually curious if a premake script can be made to generate projects across IDEs/Platforms. I also want to see if I can get a nice CodeLite setup on Linux as that's my go to IDE on that platform.

Neat. Is it possible to change the theme during runtime? Again it would be nice to have the theme of the app match the theme of the OS although there is probably no way to check this with a Linux desktop. An event(s) for theme changing would also be nice.

Ok, no problem. I just thought it was weird that it was missing while the documentation made it looked like it was a valid function.

Running current beta. This doesn't seem to work. However, this is fine. auto displays = UltraEngine::GetDisplays(); for (int k = 0; k < displays.size(); ++k) { Print("Display " + String(k) + ":"); Print(" Position: " + String(displays[k]->GetPosition())); Print(" Size: " + String(displays[k]->GetSize())); Print(" Scale: " + String(displays[k]->GetScale())); Print(" Graphics Modes:"); auto gfxmodes = displays[k]->graphicsmodes; for (int n = 0; n < gfxmodes.size(); ++n) { Print(" " + String(n) + ": " + String(gfxmodes[n])); } }

What happened to the Win32 libraries in this beta or they aren't compiled yet?

There should be a World->CountEntities() now that I think of it. You can also check the Menu.lua script as that iterates through all the entities without a Map hook to find a camera. It should use the CountEntities() function. Sorry about that.

If you are using C++, there is a vector containing all the entities in the World class. You can get the size of that. If you are using lua, I'd make a new variable and increment it with the map hook.