Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VisualServer methods are not bound #15879

Closed
Zylann opened this issue Jan 19, 2018 · 8 comments · Fixed by #15892
Closed

VisualServer methods are not bound #15879

Zylann opened this issue Jan 19, 2018 · 8 comments · Fixed by #15892

Comments

@Zylann
Copy link
Contributor

Zylann commented Jan 19, 2018

Godot 3.0 master a1c08b7

I am porting my heightmap module to GDNative, but I noticed many functions of VisualServer are not available, neither in the C++ bindings, nor in GDScript to begin with. A bunch of functions are available, but not those I need:

instance_create
instance_geometry_set_material_override
instance_set_scenario
instance_set_visible
instance_set_scenario
instance_set_transform
instance_set_base
...

The whole instance API?
They were available in 2.1.4, not in 3.0

@reduz
Copy link
Member

reduz commented Jan 19, 2018 via email

@Zylann
Copy link
Contributor Author

Zylann commented Jan 19, 2018

Where should I look for those bindings?
Edit: found them

@reduz
Copy link
Member

reduz commented Jan 19, 2018 via email

@Zylann
Copy link
Contributor Author

Zylann commented Jan 19, 2018

I noted that some methods are bound twice, like draw, sync, force_draw and force_sync

@Zylann
Copy link
Contributor Author

Zylann commented Jan 19, 2018

Can I add all other missing ones? Multimesh, Immediate, Skeleton, Light, Reflection probe, GI probe, lightmap, particles, camera, environment, scenario

@leonkrause
Copy link
Contributor

I added bindings for some VS functions a while ago. I left comments what's left to do:

// TODO: multimesh_*, immediate_*, skeleton_*, light_*, reflection_probe_*, gi_probe_*, particles_*, camera_*

// TODO: environment_*, scenario_*, instance_*

About draw and sync, you can remove the bindings missing the force_ prefix, probably just an oversight of mine

@Zylann
Copy link
Contributor Author

Zylann commented Jan 20, 2018

@eska014 why call them "force_*" if the base function isn't call that way though? Also draw and sync were existing in 2.x
I finished binding all the stuff, phew... will take some sleep before I figure out which of these duplicates to remove

@leonkrause
Copy link
Contributor

The force_ prefix makes these functions sound scarier, so users don't touch them unless they know they really need them

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants