Is there one specific nuget package I should be referencing? Or are there multiple that I need to pu
Is there one specific nuget package I should be referencing? Or are there multiple that I need to pull in?
HSilk.NET should contains all
TThank you! I initially typed in "Silk" and got all of the submodules.
TAlso I gave you a sub on YouTube, are all of your videos on making your game with Silk?
Li would reccomend against installing the big conglomerate one, and you should instead install each individual package you need
Llike Silk.NET.Windowing, Silk.NET.OpenGL, etc.
TWhy's that?
Lwaste of space on your build outputs
TAh
L- less nuget restore time
TIf I grab Silk.NET.SDL, will that just give me everything that I need for rendering, audio, windowing, etc?
TOr do I need extra packages?
Li dont think we have SDLMixer
Liirc at least
Land SDL will only work for the SDL renderer, you will need to install OpenGL/VK/DX separately to use those
Land i would reccomend using Silk.NET.Windowing if possible, not raw SDL
Lits much eaiser
Lunless you really need SDL renderer
TI don't need SDL specifically, just figured it was easiest to use
Lin that case
Lyou can ignore its existance and use Silk.NET.Windowing
Littl handle most windowing things for you
L(our SDL bindings are very not fun to use lol, they are only intended to use internally in Silk)
TAnd Silk is general-case right? Not game-dev specific. So there are no packages for physics/collision/raycasting etc?
LSilk is just bindings to various APIs with some utilities like Windowing and Math sprinkled on top, you could 100% use it for compute or something else
TI think this probably covers it:
Lprob ye
Lstuff like raycasting you'll have to do yourself, but there are some good tutorials online
TThat's what the BepuPhysics package in there is for
HNot yet but im making a game engine with it. Thanks for the sub!
HSo I have this skia renderer wrapper for my cross platform UI library, is creating the struct every frame okay?? I saw avalonia does this
Lits probably fine, but you can always just save it somewhere to be safe
HI see, thanks
Qdo I have to re-get the
KhrSwapchain extension class when I resize the window? Because it seems otherwise the maximum and minimum image sizes are equal to the old window size.
KYes, the old swap chain is out of date as any of the operations on it should report (sometimes also just non optimal). You have to recreate the swap chain. There is an option to give the old one along to not drop any frames, but usually this isn't necessary (most vulkan apps don't need super smooth resizing)
QSorry, what I meant was Silk.NET has this
Vk.TryGetDeviceExtension method, and I can get the extension interface from there. Why do I also have to re-create that? Shouldn't it always query the GPU or something?KOh sorry that's my fault, I thought you ment the SwapchainKhr Struct 
KNo the API extensions can be kept around. They would only have to be recreated when the underlying driver changes something, and that to my knowledge is never valid behavior
Qoh ... so it seems the
KhrSurface extension always returns the window size as minimum and maximum image size for GetPhysicalDeviceSurfaceCapabillities(). Not sure if that is wanted behaviour - probably is . Anyway, that's the logical error I made .KThat is entirely expected. Those are values your driver reports and seems like your driver is unable to support Swapchain sizes that don't exactly match the window size.
R"Why is resizing a swapchain intensive l only resize at 200 FPS" -some random Vulkan dev complaining on reddit
QOh that’s what it means … thanks
KIirc it can also return 0 for a dimension if there is no limit or something. Check the spec!
RSome dude on the Vulkan Reddit actually complained about that
QYep I know that; it returns max uint for that
QTbh I understand their point of view
RHow often are you going to be resizing your view over and over again, especially on Windows where the message queue is paused for the duration of the resize?
RMeaning the window literally goes inactive
SI face same thing
QWell I want to resize when the window resizes, not more often. I thought the were complaining about only supporting current window size
RNo, they're complaining about it Only resizing at 200 FPS and not whatever their previous framerate was