Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
Issue ID
1095769
Regression
No
[Windows][Standalone] The Server Build though VS Project generation does not have a command window
When generate Server Build (Headless) standalone Player on Windows, it always launches with a command window.
However, if the user generates a Visual Studio project from the Editor, then builds the Server player from VS, the Player does not launch with a command window. Instead, it can only be seen or ended in the Task Manager.
Repro:
1. Launch Unity Editor with any project on Windows
2. Choose "Server Build" and "Generate Visual Studio Project" both on Build Settings (Ctrl + Shift + B)
3. Open the VS project once it is done building in Editor
4. Build the VS project with any configuration
5. Launch the final built Player
Expected: Server Build Player launches with a comment window after built from VS project
Reality: Server Build Player does not launch with a comment window after built from VS project
Happens to: Trunk in 2019.1.0a7
Comments (32)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Resources.UnloadUnusedAssets() freezes the Editor when releasing Mesh objects
- 16-bit Sprite Textures have a banding effect and loss of data when packing into Variant Sprite Atlas
- HDRP Cluster artifacts when having more than 100 lights
- ParticleCollisionEvent.intersection generates extremely high values when particles collide while in Play Mode
- Custom attributes are not properly converted to subgraphs
Mosinmotte2
Jun 16, 2019 10:15
Source - http://www.webhostingreviewsx.co.uk/inmotion-hosting-uk-reviews/
solitairegamesfree
Apr 05, 2019 08:07
If you are searching for any type of problems, please follow these steps at http://fixwindows10connections.com will be useful for you