Using git for game development with unity for multiple platforms
I'm starting to work on a Unity game and I want to use git for version control. It's a VR game, it will have versions for all major desktop VR platforms (Oculus, Vive, WMR), where the main difference will be the SDK, but also for the upcoming Oculus Quest. This one is a standalone headset so I will have to significantly optimize different parts of the game (code, models, shaders, textures). Still, most of the assets/code will be shared with the desktop VR versions.
Ideally I'd like to keep all these versions in the same repository, but I don't know how to solve this. Initially I wanted to use multiple branches and merge into them whenever I make a "universal" change, but after reading a little bit it seems that it's strongly discouraged. I've seen some people suggest using #ifdef but this works only in code and can get pretty messy. Is there any good solution to this problem?
git unity3d version-control
asked Nov 20 at 18:28
Wojtek Wencel
76611232
|
show 1 more comment
I'm starting to work on a Unity game and I want to use git for version control. It's a VR game, it will have versions for all major desktop VR platforms (Oculus, Vive, WMR), where the main difference will be the SDK, but also for the upcoming Oculus Quest. This one is a standalone headset so I will have to significantly optimize different parts of the game (code, models, shaders, textures). Still, most of the assets/code will be shared with the desktop VR versions.
Ideally I'd like to keep all these versions in the same repository, but I don't know how to solve this. Initially I wanted to use multiple branches and merge into them whenever I make a "universal" change, but after reading a little bit it seems that it's strongly discouraged. I've seen some people suggest using #ifdef but this works only in code and can get pretty messy. Is there any good solution to this problem?
git unity3d version-control
asked Nov 20 at 18:28
Wojtek Wencel
76611232
Platform directives (such as#ifdef) and loading from AssetBundles that are made to be platform-specific would be my guess.
– Ruzihm
Nov 20 at 18:34
What do you mean by platform-specific AssetBundles? Also I would like to avoid using#ifdefif possible since it can cause some spaghetti code.
– Wojtek Wencel
Nov 20 at 18:36
2
If you want to make a single asset that compiles differently between target platform, then use platform directives. If you want to make different versions of the same asset where each one is optimized for a specific platform, make an AssetBundle for each target platform, and put all of the asset versions for that platform in that AssetBundle. You will need script to load the appropriate assetbundle & assets from it at runtime. Or you can have completely separate project dirs in the same git repository, each dir a target platform.
– Ruzihm
Nov 20 at 18:53
That's a really great solution, but I think there is one problem. Some VR sdks have to be completely excluded form the project when building it (oculus store won't accept anything with steamvr references). Asset Bundles seem to be a good solution, but then I can't really reference any of those scripts/prefabs from the bundle when creating a level for example, if I understand correctly.
– Wojtek Wencel
Nov 20 at 18:58
1
Also, there's nothing really spaghetti about platform directives if you use them to instantiate the appropriate concrete class for an interface that is common to all platforms.
– Ruzihm
Nov 20 at 18:59
|
show 1 more comment
I'm starting to work on a Unity game and I want to use git for version control. It's a VR game, it will have versions for all major desktop VR platforms (Oculus, Vive, WMR), where the main difference will be the SDK, but also for the upcoming Oculus Quest. This one is a standalone headset so I will have to significantly optimize different parts of the game (code, models, shaders, textures). Still, most of the assets/code will be shared with the desktop VR versions.
Ideally I'd like to keep all these versions in the same repository, but I don't know how to solve this. Initially I wanted to use multiple branches and merge into them whenever I make a "universal" change, but after reading a little bit it seems that it's strongly discouraged. I've seen some people suggest using #ifdef but this works only in code and can get pretty messy. Is there any good solution to this problem?
git unity3d version-control
asked Nov 20 at 18:28
Wojtek Wencel
76611232
I'm starting to work on a Unity game and I want to use git for version control. It's a VR game, it will have versions for all major desktop VR platforms (Oculus, Vive, WMR), where the main difference will be the SDK, but also for the upcoming Oculus Quest. This one is a standalone headset so I will have to significantly optimize different parts of the game (code, models, shaders, textures). Still, most of the assets/code will be shared with the desktop VR versions.
Ideally I'd like to keep all these versions in the same repository, but I don't know how to solve this. Initially I wanted to use multiple branches and merge into them whenever I make a "universal" change, but after reading a little bit it seems that it's strongly discouraged. I've seen some people suggest using #ifdef but this works only in code and can get pretty messy. Is there any good solution to this problem?
git unity3d version-control
git unity3d version-control
asked Nov 20 at 18:28
Wojtek Wencel
76611232
asked Nov 20 at 18:28
Wojtek Wencel
76611232
asked Nov 20 at 18:28
Wojtek Wencel
76611232
asked Nov 20 at 18:28
Wojtek Wencel
76611232
asked Nov 20 at 18:28
Wojtek Wencel
76611232
76611232
Platform directives (such as#ifdef) and loading from AssetBundles that are made to be platform-specific would be my guess.
– Ruzihm
Nov 20 at 18:34
What do you mean by platform-specific AssetBundles? Also I would like to avoid using#ifdefif possible since it can cause some spaghetti code.
– Wojtek Wencel
Nov 20 at 18:36
2
If you want to make a single asset that compiles differently between target platform, then use platform directives. If you want to make different versions of the same asset where each one is optimized for a specific platform, make an AssetBundle for each target platform, and put all of the asset versions for that platform in that AssetBundle. You will need script to load the appropriate assetbundle & assets from it at runtime. Or you can have completely separate project dirs in the same git repository, each dir a target platform.
– Ruzihm
Nov 20 at 18:53
That's a really great solution, but I think there is one problem. Some VR sdks have to be completely excluded form the project when building it (oculus store won't accept anything with steamvr references). Asset Bundles seem to be a good solution, but then I can't really reference any of those scripts/prefabs from the bundle when creating a level for example, if I understand correctly.
– Wojtek Wencel
Nov 20 at 18:58
1
Also, there's nothing really spaghetti about platform directives if you use them to instantiate the appropriate concrete class for an interface that is common to all platforms.
– Ruzihm
Nov 20 at 18:59
|
show 1 more comment
Platform directives (such as#ifdef) and loading from AssetBundles that are made to be platform-specific would be my guess.
– Ruzihm
Nov 20 at 18:34
What do you mean by platform-specific AssetBundles? Also I would like to avoid using#ifdefif possible since it can cause some spaghetti code.
– Wojtek Wencel
Nov 20 at 18:36
2
If you want to make a single asset that compiles differently between target platform, then use platform directives. If you want to make different versions of the same asset where each one is optimized for a specific platform, make an AssetBundle for each target platform, and put all of the asset versions for that platform in that AssetBundle. You will need script to load the appropriate assetbundle & assets from it at runtime. Or you can have completely separate project dirs in the same git repository, each dir a target platform.
– Ruzihm
Nov 20 at 18:53
That's a really great solution, but I think there is one problem. Some VR sdks have to be completely excluded form the project when building it (oculus store won't accept anything with steamvr references). Asset Bundles seem to be a good solution, but then I can't really reference any of those scripts/prefabs from the bundle when creating a level for example, if I understand correctly.
– Wojtek Wencel
Nov 20 at 18:58
1
Also, there's nothing really spaghetti about platform directives if you use them to instantiate the appropriate concrete class for an interface that is common to all platforms.
– Ruzihm
Nov 20 at 18:59
Platform directives (such as
#ifdef) and loading from AssetBundles that are made to be platform-specific would be my guess.– Ruzihm
Nov 20 at 18:34
Platform directives (such as
#ifdef) and loading from AssetBundles that are made to be platform-specific would be my guess.– Ruzihm
Nov 20 at 18:34
What do you mean by platform-specific AssetBundles? Also I would like to avoid using
#ifdef if possible since it can cause some spaghetti code.– Wojtek Wencel
Nov 20 at 18:36
What do you mean by platform-specific AssetBundles? Also I would like to avoid using
#ifdef if possible since it can cause some spaghetti code.– Wojtek Wencel
Nov 20 at 18:36
2
2
If you want to make a single asset that compiles differently between target platform, then use platform directives. If you want to make different versions of the same asset where each one is optimized for a specific platform, make an AssetBundle for each target platform, and put all of the asset versions for that platform in that AssetBundle. You will need script to load the appropriate assetbundle & assets from it at runtime. Or you can have completely separate project dirs in the same git repository, each dir a target platform.
– Ruzihm
Nov 20 at 18:53
If you want to make a single asset that compiles differently between target platform, then use platform directives. If you want to make different versions of the same asset where each one is optimized for a specific platform, make an AssetBundle for each target platform, and put all of the asset versions for that platform in that AssetBundle. You will need script to load the appropriate assetbundle & assets from it at runtime. Or you can have completely separate project dirs in the same git repository, each dir a target platform.
– Ruzihm
Nov 20 at 18:53
That's a really great solution, but I think there is one problem. Some VR sdks have to be completely excluded form the project when building it (oculus store won't accept anything with steamvr references). Asset Bundles seem to be a good solution, but then I can't really reference any of those scripts/prefabs from the bundle when creating a level for example, if I understand correctly.
– Wojtek Wencel
Nov 20 at 18:58
That's a really great solution, but I think there is one problem. Some VR sdks have to be completely excluded form the project when building it (oculus store won't accept anything with steamvr references). Asset Bundles seem to be a good solution, but then I can't really reference any of those scripts/prefabs from the bundle when creating a level for example, if I understand correctly.
– Wojtek Wencel
Nov 20 at 18:58
1
1
Also, there's nothing really spaghetti about platform directives if you use them to instantiate the appropriate concrete class for an interface that is common to all platforms.
– Ruzihm
Nov 20 at 18:59
Also, there's nothing really spaghetti about platform directives if you use them to instantiate the appropriate concrete class for an interface that is common to all platforms.
– Ruzihm
Nov 20 at 18:59
|
show 1 more comment
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53399291%2fusing-git-for-game-development-with-unity-for-multiple-platforms%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53399291%2fusing-git-for-game-development-with-unity-for-multiple-platforms%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Platform directives (such as
#ifdef) and loading from AssetBundles that are made to be platform-specific would be my guess.– Ruzihm
Nov 20 at 18:34
What do you mean by platform-specific AssetBundles? Also I would like to avoid using
#ifdefif possible since it can cause some spaghetti code.– Wojtek Wencel
Nov 20 at 18:36
2
If you want to make a single asset that compiles differently between target platform, then use platform directives. If you want to make different versions of the same asset where each one is optimized for a specific platform, make an AssetBundle for each target platform, and put all of the asset versions for that platform in that AssetBundle. You will need script to load the appropriate assetbundle & assets from it at runtime. Or you can have completely separate project dirs in the same git repository, each dir a target platform.
– Ruzihm
Nov 20 at 18:53
That's a really great solution, but I think there is one problem. Some VR sdks have to be completely excluded form the project when building it (oculus store won't accept anything with steamvr references). Asset Bundles seem to be a good solution, but then I can't really reference any of those scripts/prefabs from the bundle when creating a level for example, if I understand correctly.
– Wojtek Wencel
Nov 20 at 18:58
1
Also, there's nothing really spaghetti about platform directives if you use them to instantiate the appropriate concrete class for an interface that is common to all platforms.
– Ruzihm
Nov 20 at 18:59