Visual Studio Code can be a great companion to Unity for editing and debugging C# files. All of the C# features are supported and more. In the screen below, you can see code colorization, bracket matching, IntelliSense, CodeLens and that's just the start.

Read on to find out how to configure Unity and your project to get the best possible experience.

Missing the textures off your FBX import into Unity? Never fear, there are still there you just need to know where.

Prerequisites

From Using .NET Core in Visual Studio Code:

1. Install .NET Core, both the Runtime and the SDK, which includes the dotnet command.

2. [Windows only] Logout or restart Windows to allow changes to %PATH% to take effect.

3. [macOS only] To avoid seeing 'Some projects have trouble loading. Please review the output for more details', make sure to install the latest stable Mono release.

   Note: This version of Mono, which is installed into your system, will not interfere with the version of MonoDevelop that is installed by Unity.

4. Install the C# extension from the VS Code Marketplace.

Setup VS Code as Unity Script Editor

Open up Unity Preferences, External Tools, then browse for the Visual Studio Code executable as External Script Editor.

The Visual Studio Code executable can be found at /Applications/Visual Studio Code.app on macOS, C:users{username}AppDataLocalProgramsMicrosoft VS CodeCode.exe on Windows by default.

Unity has built-in support for opening scripts in Visual Studio Code as an external script editor on Windows and macOS. Unity will detect when Visual Studio Code is selected as an external script editor and pass the correct arguments to it when opening scripts from Unity. Unity will also set up a default .vscode/settings.json with file excludes, if it does not already exist (from Unity 5.5 Release notes).

Editing Evolved

With the solution file selected, you are now ready to start editing with VS Code. Here is a list of some of the things you can expect:

• Syntax Highlighting
• Bracket matching
• IntelliSense
• Snippets
• CodeLens
• Peek
• Go-to Definition
• Code Actions/Lightbulbs
• Go to symbol
• Hover

Two topics that will help you are Basic Editing and C#. In the image below, you can see VS Code showing hover context, peeking references and more.

Unity Extensions

The community is continually developing more and more valuable extensions for Unity. Here are some popular extensions that you might find useful. You can search for more extensions in the VS Code Extension Marketplace.

The extensions shown above are dynamically queried. Click on an extension tile above to read the description and reviews to decide which extension is best for you. See more in the Marketplace.

Enabling code completion (For recent versions of Unity)

If you are installing VS Code for the first time, you might be missing targeting packs required for Unity's code-completion (IntelliSense) in VS Code.

Targeting pack download links:

Steps:

1. Stop VS Code or Unity running.
2. Download and install the targeting pack for your targeted framework version / preferred version from one of the above links.
3. Start Unity.
4. Create and/or open an existing script in VS Code, through Unity, and you should now see code completions.

Next steps

Read on to learn more about:

• Basic Editing - Learn about the powerful VS Code editor.
• Code Navigation - Move quickly through your source code.
• Debugging - how to use the debugger with your project
• C# - learn about the C# support in VS Code

Common questions

I don't have IntelliSense

You need to ensure that your solution is open in VS Code (not just a single file). Open the folder with your solution and you usually will not need to do anything else. If for some reason VS Code has not selected the right solution context, you can change the selected project by clicking on the OmniSharp flame icon on the status bar.

Choose the -CSharp version of the solution file and VS Code will light up.

How can I change the file exclusions?

Unity creates a number of additional files that can clutter your workspace in VS Code. You can easily hide these so that you can focus on the files you actually want to edit.

To do this, add the following JSON to your workspace settings.

As you can see below this will clean things up a lot..

How can I debug Unity?

Install the Debugger for Unity extension. And check out Debugging with VS Code to learn more about VS Code debugging support.

Unity FBX Exporter (1.2.0)

GitHub: https://github.com/KellanHiggins/UnityFBXExporterContact: unityfbxexporter@8bitgoose.com

The Unity FBX Exporter is a simple FBX writer designed to export static objects from Unity into the FBX format, preserving the materials, game object hierarchy and textures attached.

It was written for the Unity asset Building Crafter (http://u3d.as/ovC) which allows anyone using Unity to create buildings right in Unity without any modeling experience.

Features

1. Can export any GameObject into FBX format.

2. Supports FBX format 7.3, around 2013.

3. Exports materials into the FBX file.

4. Exports texture references into the FBX file.

5. Can make a copy of all materials and link them to newly minted FBX file.

6. Can make a copy of all textures and link them to newly create materials.

7. Export very deeply hierarchical Game Objects with just a few clicks.

8. Objects will export their rotation correctly throughout the hierarchy (thanks @quickfingerz on Github).

9. Objects will also export their scale correctly (thanks @quickfingerz on Github).

Known limitations

1. FBX format will only recognize diffuse maps and normal maps when exporting. Can not include height maps, for example.

2. Textures only support PBR Unity 5 shaders.

3. Only exports one UV map, not a AO UV 2 map.

4. Sort of works at Runtime. Needs to use File.IO instead of AssetDatabase to truly work at runtime.

5. Sometimes the reimported FBX files don't find the right materials. C'est la vie.

6. Exporting a prefab in the Project Tab sort of works. Needs more testing

Tutorial

It is very simple to use this exporter. You shouldn't have any problems, and if you do, please add an issue to the Github project

1. Select any GameObject in the scene.

2. Select the type of export you'd like

   The excel plug in is not supported for Apple computers; it will work if you have a Windows partition on your Mac. If the latest version of Capital IQ does not work with your operating system you may have to install an earlier version. From the downloads page click on Advanced Office Downloads. Academic accounts do not have access to the iPad, iPhone or Android apps. Manuals and documentation can be found by logging into Capital IQ and clicking on Help at the top right of the screen. The excel plug in is not supported for Apple computers; it will work if you have a Windows partition on your Mac. If the latest version of Capital IQ does not work with your operating system you may have to install an earlier version. From the downloads page click on Advanced Office Downloads. Capitaliq.

3. 'Only GameObject' will export a new FBX but not create any new materials or textures and use the original as reference

   Weed games for mac. Hempire – Weed Growing Game Download For PC: From ganja to glory – get ready to grow your operation into a mighty Hempire! This is the ultimate weed growing game. It doesn’t just stop at the pot: you must harvest your plants, breed new and unusual strains, make friends (and enemies), and eventually take control of your entire home city to be victorious. Download Hempire - Weed Growing Game and enjoy it on your iPhone, iPad, and iPod touch. ‎Welcome to Hempire: The World’s Greatest Weed Growing Game & Community Let’s Grow!.Grow weed and popular strains like Northern Lights, Hindu Kush, Jack Herer, and many more!

4. 'With new Materials' will export a new FBX and create new materials with the GameObject name + _ + material name

5. 'With new Materials and Textures' does 2b plus copying textures to a new folder. This one takes a while. Be patient.

6. Wait a bit

7. If you've selected new textures, wait a bit longer. Copying and reimporting the textures takes Unity's brainpower.

8. Check the folder.

9. Usually the materials will align, but if you have a FBX in the root area it may create new materials instead of finding the old ones.

10. Success! You now have a brand new FBX file with everything parented correctly. Remember rotations in children still don't work.

NOTE: Sometimes the fbx file imports the materials as recursive instead of project wide for GameObject only export. If this happens, delete all the materials and reimport the FBX file using Project-Wide for material search.

Maya

This was created without owning Maya, so please give feedback on how opening these FBX files work. You can give feedback at unityfbxexporter@8bitgoose.com.

Export to Blender

Blender 2.70 doesn't take ASCII FBX files. So you'll need to download the converter from the FBX site. Then convert it to a binary file and then import it into blender. Because the relative texture names are correct, blender will import your albedo and normal texture. Pretty neat!

Known Issues

1. Skinned mesh renderers may or may not be exporting materials correctly. Did not work on my test object.
2. Standard objects throw an error if you try and export them (like the sphere). Still seems to export fine. Also why are you exporting Unity's sphere???

Crediting This Project

As a note, this project is an MIT license. Which means you can take this code, upload it to the Unity Asset store and charge money for it. BUT, you must include the license (including the bit about Building Crafter) in your project. If you have any questions about this, hit me up.

If you compact it into a DLL and hide all the code away, you still have to include the license somewhere. I'd much rather you come to me then find out you've taken in 4 months later. Don't be a dick, give back to the community!

Change log

Version 1.2.0

1. Thanks to @tetreum for fixing my bad tutorial.

2. Also thanks to @tetreum for preventing copying non existent items

3. Thanks to @cartzhang for adding skinned mesh render exporter

4. Thanks to @mikelortega for fixing crash from trying to export materials that are procedurally generated

5. Thanks to @Totchinuko for adding awesome vertex colour export

6. Added an export option from the GameObject menu

7. And thanks to @MadmenAlliance for putting this up on the asset store without proper attribution which forced me to get my ass in gear and pull in all these changes

Version 1.1.1

1. Hotfix for something.

Version 1.1.0

1. Thanks to @quickfingerz for fixing the rotation export so it looks right in the FBX file.

Versin 1.0.0

1. Initial release