as good as wine has become, its still not a 'just works' solution
as good as wine has become, its still not a 'just works' solution
P
Pthat's going to become less and less of a problem over time though
AYea wine is not a great choice for development
I mostly need dxvk to develop DX apilications without booting into windows
I mostly need dxvk to develop DX apilications without booting into windows
Sit looks weird,atleast for me cuz i used opengl alot
Plook how far it's come since the steam machine launched
Lunfortanately that doesnt solve the runtime compilation issue
APart of the weirdness may be down to the fact that I use it in a very unconventional way in order to allow both GL and D3D to work together in one package without any code changes
AYou need to work around some things etc
Pi'm currently working on a d3d11 hello quad example
Pso stay tuned
ANice
Snice
AWill be nice to switch to silk for d3d bindings too
Lsame
ASince that is part of the reason I switched to silk in the first place
Li was hoping to switch to silk for d3d9 but uhhhhhhhhh
Lim good
ALmao
Lid fix it myself if buildtools didnt hate me
Swhat did you use before?
Aopentk
Show was it?
AFine? Not really sure how to answer that
Si could say the same
ASwitching to silk with unsafe took a bit of time and a few driver crashes but it was easy enough
Now I don't even think about it, I just know when to use unsafe and when not to
Now I don't even think about it, I just know when to use unsafe and when not to
Si switched to silk from opentk cuz my friend told me to use vulkan instead of opengl(spoiler alert:i didn't use vulkan)
LVulkan is unnessesary for 99% of people
AYes
PGenerally when people are questioning whether to use Silk.NET, I find that a lot of people's reservations either come from the project's age and/or the level of documentation. Neither of which are going to be solved in any trivial amount of time, so I just tend to recommend OpenTK to those people. You do have to make concessions on the documentation front for Silk.NET, and only you can decide whether that's worth it. A lot of people are also beginners hence why I just flat out recommend OpenTK in those cases where they could clearly do with good documentation.
ATelling someone to use Vulkan over OpenGL is like telling someone to cook a meal vs a microwave dinner
Can you? Yes.
Is it easy? No.
Should you? Depends.
Can you? Yes.
Is it easy? No.
Should you? Depends.
Si think the only good use for vulkan is for consoles
PI'm a microwave dinner person myself.
Lthats not really true
Pwell that's... i mean exactly zero consoles use Vulkan as their preferred/native API
L(do most consoles even support vulkan?)
Pand even then Nintendo Switch is the only console that "supports" Vulkan
Si swear thanks to this server,i learn more stuff about opengl and vulkan
P(I guess you can count the Steam Deck, but I do think of that as more of a PC)
Sliterally just steam but an os
Pi know, i have one 
AFinally enough I spent a lot of time comparing silk vs OpenTK when I was first learning OpenGL.
Like a serious amount of time
I only joined a couple months ago but my "relationship" with silk spans almost 2 years.
I spent a fair amount of time trying both OpenTK and silk but I eventually settled on OpenTK cause I had next to no C# knowledge and unsafe just made scream lmao
Like a serious amount of time
I only joined a couple months ago but my "relationship" with silk spans almost 2 years.
I spent a fair amount of time trying both OpenTK and silk but I eventually settled on OpenTK cause I had next to no C# knowledge and unsafe just made scream lmao
LVulkan is absolutely great if you need good multithreaded rendering and low CPU overhead
AAnd learning GL on top of this made me almost die inside
I almost lost my head trying to learn GL until one day it randomly clicked and I've not looked back since
I almost lost my head trying to learn GL until one day it randomly clicked and I've not looked back since
AI agree.
Unfortunately, this is where I've hit a snag with GL
I do now need multkthreading
Not right now but I will do.
Well
Can't actually guarantee I will
Just kinda assuming with the vision I have multkthreading will very much improve performance a lot
Unfortunately, this is where I've hit a snag with GL
I do now need multkthreading
Not right now but I will do.
Well
Can't actually guarantee I will
Just kinda assuming with the vision I have multkthreading will very much improve performance a lot
Pis unsafe really that bad with OpenGL? i swear OpenGL is the only place where the overloader actually does sensible things
AUnsafe is fine now
Por does the non-unsafe stuff just have really poor visibility
Pok let me rephrase
AOh
Pis unsafe code really that unavoidable?
