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
Issue or just understanding? #37
Comments
Only one scripts folder is recognized by the exporter, but it can be easily modified to fit your needs (check ExportSceneWizard.cs and the Exporter project). In the project I am working on I have all those script subfolders directly under Scripts. This is a little worse than what I used to do (each specific enough object with its own Scripts subfolder, plus a common folder for shared scripts), but it works quite well with a little bit of organization. I also store libraries as sources inside a subfolder in Scripts, although I am having some issues with using directives not being ported to XNA. |
I haven't tried this, but I think that if you just leave the scripts Sendt fra min Windows Phone Do the scripts all have to be in a single scripts folder? I often have -- Models I guess what I am asking is how can I add multiple paths to the script Reply to this email directly or view it on GitHub: |
I went through getting started and with the example in the framework I did get my scene to pretty much load. I do have a few questions but one at a time.
Do the scripts all have to be in a single scripts folder? I often have a layout like this
-- Models
----modelA
----modelB
----etc
--Scene
----SceneA
----SceneB
--Scripts
----script
----script
----FOLDER
-------some other script
-------script
--2Dscripts
----script
----script
--prefabs
----thing
----thing
----FOLDER
I guess what I am asking is how can I add multiple paths to the script field in the converter? Will the converter read all sub folders and scripts? The same question would go for scenes etc.
The text was updated successfully, but these errors were encountered: