Jump to content
Happy Holidays! Limited Staff Responses: 1/20 - 1/31 ×

Viveport Unity App Submission Manifest


Medis

Recommended Posts

Hello,
We have a problem with the submition of the app. i check the documentation and said to change some manifest file which i cant find... Can someone send me some form of guide how to export the app from unity to viveport? At least the basic steps.

Thanks
Kostas

Link to comment
Share on other sites

Hi ,

 

First of all if you haven't seen it, download the Viveport Submission Guide for a lot of details.

 

 

Here are some more specific steps for you.

 

First, you should compile your final EXE and/or assets folder(s) from Unity. Then, you'll be zipping all of those up into one ZIP, which is what you'll upload via the developer console.

 

When you get to the step in the process named 'Binary Build', you'll click in the text window to see an auto-created content manifest. This is created using the content ID that's generated when you first uploaded / named your Viveport submission.

 

Something that can confuse is where the 'binary_path_windows' line is, and what you need to put in there. This is the path to where your EXE file is found within your ZIP file. Once you click on the manifest to generate it, here's a screenshot of what you should see - I've outlined the specific line in red:

 



 

 

You're going to modify that line directly inside the text box - you don't need to change anything else. (Your content manifest will not look exactly like this one as your variables are different.) As for what you'll put in the binary path line, that varies depending on your file structure.

 

When you only have an EXE file and it's in the root directory of your ZIP file, you'd simply place that within the " " after the "binary_path_windows" line. So for a file named 'coolVR.exe', as described in the documentation, the binary path line would look like this:

 

"binary_path_windows":"coolVR.exe",

 

If you have data folders, you need to create a folder structure for your EXE. The complete file structure is 'appname\Binaries\Win64\appname.exe', where appname is your EXE name. So you'll create a folder in the root named after whatever your EXE is called (just the EXE name, not appname.exe), a folder inside that called Binaries, and a folder inside Binaries named Win64 - in which you put your EXE file.

 

Final result, again using the 'CoolVR.EXE' example, the binary path line in your manifest would look like this. Note the double slashes!

 

"binary_path_windows":"coolVR\\Binaries\\Win64\\coolVR.exe",

 

Last but not least - the total character count of the file location (i.e. what's contained between the quote marks starting with 'coolVR' above) cannot be above 72 total. The good news is that the slashes only count as 1 character each. In the example above, counting the slashes brings us to 35, but removing 1 character count per slash brings it back to 32.

 

Simple rule of thumb: don't make an overly long EXE name and you should be fine. :)

 

Finally, remember our submissions are reviewed by real humans. If you make an error in the manifest path they'll help correct it for you.

 

Hope that helps!

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...