home.social

#gdextension — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #gdextension, aggregated by home.social.

  1. So now I want to make this into a #GDExtension. The problem is that I don't know #CPlusPlus... I am going through what's in learncpp.com but it's really oriented towards people who are way less experienced than I am at general programming, which is annoying because I have to skim a lot and it is a waste of time plus there's a risk of missing something important. I looked at some books, but everything I saw seemed pretty heavily oriented towards systems/low-level programming or, if it's a #GameDev book, towards building your own engine, which is not what I need right now. If I wanted to make everything from scratch, I'd just use Rust...

    Does anyone have a resource to recommend that would be appropriate? Something that will help me understand the higher level features of C++, classes, interfaces, things to watch out for and things to know... Also how to structure a program, compiling tips, working with macros, etc.

    #Godot

  2. So now I want to make this into a #GDExtension. The problem is that I don't know #CPlusPlus... I am going through what's in learncpp.com but it's really oriented towards people who are way less experienced than I am at general programming, which is annoying because I have to skim a lot and it is a waste of time plus there's a risk of missing something important. I looked at some books, but everything I saw seemed pretty heavily oriented towards systems/low-level programming or, if it's a #GameDev book, towards building your own engine, which is not what I need right now. If I wanted to make everything from scratch, I'd just use Rust...

    Does anyone have a resource to recommend that would be appropriate? Something that will help me understand the higher level features of C++, classes, interfaces, things to watch out for and things to know... Also how to structure a program, compiling tips, working with macros, etc.

    #Godot

  3. So now I want to make this into a #GDExtension. The problem is that I don't know #CPlusPlus... I am going through what's in learncpp.com but it's really oriented towards people who are way less experienced than I am at general programming, which is annoying because I have to skim a lot and it is a waste of time plus there's a risk of missing something important. I looked at some books, but everything I saw seemed pretty heavily oriented towards systems/low-level programming or, if it's a #GameDev book, towards building your own engine, which is not what I need right now. If I wanted to make everything from scratch, I'd just use Rust...

    Does anyone have a resource to recommend that would be appropriate? Something that will help me understand the higher level features of C++, classes, interfaces, things to watch out for and things to know... Also how to structure a program, compiling tips, working with macros, etc.

    #Godot

  4. So now I want to make this into a . The problem is that I don't know ... I am going through what's in learncpp.com but it's really oriented towards people who are way less experienced than I am at general programming, which is annoying because I have to skim a lot and it is a waste of time plus there's a risk of missing something important. I looked at some books, but everything I saw seemed pretty heavily oriented towards systems/low-level programming or, if it's a book, towards building your own engine, which is not what I need right now. If I wanted to make everything from scratch, I'd just use Rust...

    Does anyone have a resource to recommend that would be appropriate? Something that will help me understand the higher level features of C++, classes, interfaces, things to watch out for and things to know... Also how to structure a program, compiling tips, working with macros, etc.

  5. So now I want to make this into a #GDExtension. The problem is that I don't know #CPlusPlus... I am going through what's in learncpp.com but it's really oriented towards people who are way less experienced than I am at general programming, which is annoying because I have to skim a lot and it is a waste of time plus there's a risk of missing something important. I looked at some books, but everything I saw seemed pretty heavily oriented towards systems/low-level programming or, if it's a #GameDev book, towards building your own engine, which is not what I need right now. If I wanted to make everything from scratch, I'd just use Rust...

    Does anyone have a resource to recommend that would be appropriate? Something that will help me understand the higher level features of C++, classes, interfaces, things to watch out for and things to know... Also how to structure a program, compiling tips, working with macros, etc.

    #Godot

  6. I was looking for a Queue type but couldn't find one, so I wrote one and if you have a better idea, I'd love to hear it!
    codeberg.org/anyreso/godot-que

    #godot #godotengine #gdextension

  7. I was looking for a Queue type but couldn't find one, so I wrote one and if you have a better idea, I'd love to hear it!
    codeberg.org/anyreso/godot-que

    #godot #godotengine #gdextension

  8. Is anyone here secretly a godot C++ / GDExtension wizard? I'd love to ask some questions and finally understand the meaning of the universe

    #Godot4 #gdextension

  9. Is anyone here secretly a godot C++ / GDExtension wizard? I'd love to ask some questions and finally understand the meaning of the universe

    #Godot4 #gdextension

  10. Is anyone here secretly a godot C++ / GDExtension wizard? I'd love to ask some questions and finally understand the meaning of the universe

    #Godot4 #gdextension

  11. Is anyone here secretly a godot C++ / GDExtension wizard? I'd love to ask some questions and finally understand the meaning of the universe

    #Godot4 #gdextension

  12. Nice to see how stable GDExtension (and its godot-cpp bindings) are API-wise. Upgrading my MODs-playing GDExtension (github.com/oparisy/gdextension) to Godot 4.3 was straightforward

    I even briefly tested backward compatibility by testing my 4.2 compiled module on Godot 4.3, and it worked flawlessly.

    #godotengine #gdextension

  13. Nice to see how stable GDExtension (and its godot-cpp bindings) are API-wise. Upgrading my MODs-playing GDExtension (github.com/oparisy/gdextension) to Godot 4.3 was straightforward

    I even briefly tested backward compatibility by testing my 4.2 compiled module on Godot 4.3, and it worked flawlessly.

    #godotengine #gdextension

  14. Finally had time to work on the #Godot4 #gdextension version of rope3d, you can't find a preview in the godot asset lib yet, but you CAN find it here: github.com/tcmug/godot_rope3d

    If you wanna join and help please do!

    #godotengine #gamedev

  15. Finally had time to work on the #Godot4 #gdextension version of rope3d, you can't find a preview in the godot asset lib yet, but you CAN find it here: github.com/tcmug/godot_rope3d

    If you wanna join and help please do!

    #godotengine #gamedev

  16. Finally had time to work on the #Godot4 #gdextension version of rope3d, you can't find a preview in the godot asset lib yet, but you CAN find it here: github.com/tcmug/godot_rope3d

    If you wanna join and help please do!

    #godotengine #gamedev

  17. Finally had time to work on the #Godot4 #gdextension version of rope3d, you can't find a preview in the godot asset lib yet, but you CAN find it here: github.com/tcmug/godot_rope3d

    If you wanna join and help please do!

    #godotengine #gamedev

  18. Finally had time to work on the #Godot4 #gdextension version of rope3d, you can't find a preview in the godot asset lib yet, but you CAN find it here: github.com/tcmug/godot_rope3d

    If you wanna join and help please do!

    #godotengine #gamedev

  19. As I sit down here going back to work taking a chainsaw deep into toyBrot, it occurs to me that maybe some of you may not have checked out last Friday's blog post!

    If you were considering dipping your toes into #GodotEngine #GDExtension for your #cpp shenanigans, then this could interest you!

    It's going to be followed up this Friday too by a part 2 about the CMake and general project structure side of things. Better catch up on part 1 while there's time =P

    vilelasagna.ddns.net/coding/br

  20. As I sit down here going back to work taking a chainsaw deep into toyBrot, it occurs to me that maybe some of you may not have checked out last Friday's blog post!

    If you were considering dipping your toes into #GodotEngine #GDExtension for your #cpp shenanigans, then this could interest you!

    It's going to be followed up this Friday too by a part 2 about the CMake and general project structure side of things. Better catch up on part 1 while there's time =P

    vilelasagna.ddns.net/coding/br

  21. As I sit down here going back to work taking a chainsaw deep into toyBrot, it occurs to me that maybe some of you may not have checked out last Friday's blog post!

    If you were considering dipping your toes into #GodotEngine #GDExtension for your #cpp shenanigans, then this could interest you!

    It's going to be followed up this Friday too by a part 2 about the CMake and general project structure side of things. Better catch up on part 1 while there's time =P

    vilelasagna.ddns.net/coding/br

  22. As I sit down here going back to work taking a chainsaw deep into toyBrot, it occurs to me that maybe some of you may not have checked out last Friday's blog post!

    If you were considering dipping your toes into #GodotEngine #GDExtension for your #cpp shenanigans, then this could interest you!

    It's going to be followed up this Friday too by a part 2 about the CMake and general project structure side of things. Better catch up on part 1 while there's time =P

    vilelasagna.ddns.net/coding/br

  23. As I sit down here going back to work taking a chainsaw deep into toyBrot, it occurs to me that maybe some of you may not have checked out last Friday's blog post!

    If you were considering dipping your toes into #GodotEngine #GDExtension for your #cpp shenanigans, then this could interest you!

    It's going to be followed up this Friday too by a part 2 about the CMake and general project structure side of things. Better catch up on part 1 while there's time =P

    vilelasagna.ddns.net/coding/br

  24. And, whew, there we go!

    We got text in pararaphs, on a webpage, with pictures, with code snippets, with links, the whole shebang!

    There's plenty of time for more thorough proof reading and adjustments until then but NEXT Friday's blog post is basically done!

    Make sure you're ready for it by reading today's post about the C++ side of working in #GodotEngine with #GDExtension

    vilelasagna.ddns.net/coding/br

  25. And, whew, there we go!

    We got text in pararaphs, on a webpage, with pictures, with code snippets, with links, the whole shebang!

    There's plenty of time for more thorough proof reading and adjustments until then but NEXT Friday's blog post is basically done!

    Make sure you're ready for it by reading today's post about the C++ side of working in #GodotEngine with #GDExtension

    vilelasagna.ddns.net/coding/br

  26. And, whew, there we go!

    We got text in pararaphs, on a webpage, with pictures, with code snippets, with links, the whole shebang!

    There's plenty of time for more thorough proof reading and adjustments until then but NEXT Friday's blog post is basically done!

    Make sure you're ready for it by reading today's post about the C++ side of working in #GodotEngine with #GDExtension

    vilelasagna.ddns.net/coding/br

  27. And, whew, there we go!

    We got text in pararaphs, on a webpage, with pictures, with code snippets, with links, the whole shebang!

    There's plenty of time for more thorough proof reading and adjustments until then but NEXT Friday's blog post is basically done!

    Make sure you're ready for it by reading today's post about the C++ side of working in #GodotEngine with #GDExtension

    vilelasagna.ddns.net/coding/br

  28. And, whew, there we go!

    We got text in pararaphs, on a webpage, with pictures, with code snippets, with links, the whole shebang!

    There's plenty of time for more thorough proof reading and adjustments until then but NEXT Friday's blog post is basically done!

    Make sure you're ready for it by reading today's post about the C++ side of working in #GodotEngine with #GDExtension

    vilelasagna.ddns.net/coding/br

  29. It feels good to be on schedule. Just finished writing the draft for the next blog post, the one that talks about CMake and IDE setup for building #GDExtension projects

    Could be just the high and all but I think I like it even more than the one that got published today

  30. It feels good to be on schedule. Just finished writing the draft for the next blog post, the one that talks about CMake and IDE setup for building #GDExtension projects

    Could be just the high and all but I think I like it even more than the one that got published today

  31. It feels good to be on schedule. Just finished writing the draft for the next blog post, the one that talks about CMake and IDE setup for building #GDExtension projects

    Could be just the high and all but I think I like it even more than the one that got published today

  32. This "build your #GDExtension with #CMake " post is kiiind of turning into #QtCreator propaganda just a bit

    I will not apologise

  33. This "build your #GDExtension with #CMake " post is kiiind of turning into #QtCreator propaganda just a bit

    I will not apologise

  34. This "build your #GDExtension with #CMake " post is kiiind of turning into #QtCreator propaganda just a bit

    I will not apologise

  35. I keep forgetting that me boosting my blog doesn't quite make it go on Local. Still, this week's post is all about the C++ side of playing with #GodotEngine #GDExtension

    So I dunno, maybe it's interesting to someone around these parts

    mastodon.gamedev.place/@tgr@vi

  36. I keep forgetting that me boosting my blog doesn't quite make it go on Local. Still, this week's post is all about the C++ side of playing with #GodotEngine #GDExtension

    So I dunno, maybe it's interesting to someone around these parts

    mastodon.gamedev.place/@tgr@vi

  37. I keep forgetting that me boosting my blog doesn't quite make it go on Local. Still, this week's post is all about the C++ side of playing with #GodotEngine #GDExtension

    So I dunno, maybe it's interesting to someone around these parts

    mastodon.gamedev.place/@tgr@vi

  38. This pair of posts is about me trying out #GDExtension

    Tomorrow it's all about the C++ side, I go kind of step by step on the #GodotEngine Nodes I wrote to wrap toyBrot's std::threads and OpenCL implementations

    This next one is going to be about the CMake side of things and general project considerations and pitfalls. Directory structure, debugging, this sort of stuff

  39. This pair of posts is about me trying out #GDExtension

    Tomorrow it's all about the C++ side, I go kind of step by step on the #GodotEngine Nodes I wrote to wrap toyBrot's std::threads and OpenCL implementations

    This next one is going to be about the CMake side of things and general project considerations and pitfalls. Directory structure, debugging, this sort of stuff

  40. This pair of posts is about me trying out #GDExtension

    Tomorrow it's all about the C++ side, I go kind of step by step on the #GodotEngine Nodes I wrote to wrap toyBrot's std::threads and OpenCL implementations

    This next one is going to be about the CMake side of things and general project considerations and pitfalls. Directory structure, debugging, this sort of stuff

  41. Okay, it's time to cut my losses. I've got C++ threads and OpenCL toyBrot working as #GDExtension which is hype BUT I'm running into this exact thing where godot::Image is apparently not auto-registering in #GodotEngine ClassDB. I've been fiddling about but couldn't trick it into working. So it's going to stay like this for now. No nasty side-effects for me, except for console pollution. Enough for me to finally get to writing

    Same issue as this
    github.com/godotengine/godot-c

  42. Okay, it's time to cut my losses. I've got C++ threads and OpenCL toyBrot working as #GDExtension which is hype BUT I'm running into this exact thing where godot::Image is apparently not auto-registering in #GodotEngine ClassDB. I've been fiddling about but couldn't trick it into working. So it's going to stay like this for now. No nasty side-effects for me, except for console pollution. Enough for me to finally get to writing

    Same issue as this
    github.com/godotengine/godot-c

  43. Okay, it's time to cut my losses. I've got C++ threads and OpenCL toyBrot working as #GDExtension which is hype BUT I'm running into this exact thing where godot::Image is apparently not auto-registering in #GodotEngine ClassDB. I've been fiddling about but couldn't trick it into working. So it's going to stay like this for now. No nasty side-effects for me, except for console pollution. Enough for me to finally get to writing

    Same issue as this
    github.com/godotengine/godot-c

  44. Heck yeah! After a decent amount of back and forth trying to understand exactly what is actually implemented or called where, looks like my ostream is finally working.

    Normally just pipes straight into std::cout, but if I set the define to tell it it's a #GDExtension and this is a debug build, it just calls #GodotEngine print() on flush.

    There's a handful of edges to smooth still but quite happy with where it's going

    gitlab.com/VileLasagna/toyBrot

    gitlab.com/VileLasagna/toyBrot