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

unity stand alone build support + unity editor mesh duplicate #507

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

MyelinsheathXD
Copy link

  1. stand alone unity build support . encapsulated all editor scripts with #if UNITY_EDITOR
    since mujoco namespace holding editor modules which cases to error during stanablone build

MyelinsheathXD@72618db

  1. On geometry duplicate, the visable mesh disappear in the editor. On duplicate phase in the editor , ExecuteinedinMode along with Update method removing original shared mesh on duplicate phase
    fixed by calling DestroyImmediate() only when Aplication is in Play mode

MyelinsheathXD@100ad5c

the branch fork link https://github.com/MyelinsheathXD/mujocoGameTools/tree/v2.1.5fromComUnity

converted all editor scripts with
#if UNITY_EDITOR
#endif

since they all are namespace which interfaces during runtime in build phase
with [Executeiniditmode] during dublication  protedted void Update is being called on the new clones gameobject, which causing to delete the mesh on original gameobject. But after play mode mesh comes back

permanent fix is : call destroy   DisposeCurrentMesh() only in application is in play mode
@google-cla
Copy link

google-cla bot commented Sep 28, 2022

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@saran-t saran-t requested a review from erez-tom October 6, 2022 12:46
@Balint-H
Copy link
Contributor

Isn't addition 1 already addressed by 0180d83?

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

Successfully merging this pull request may close these issues.

None yet

2 participants