Search Issue Tracker
Fixed in 2019.1.X
Votes
2
Found in
5.3.5p5
Issue ID
817995
Regression
No
[Standalone] Force Single Instance ignored when launching from a batch
1. Open "case_817995-MultipleInstances/Build" folder.
2. Try to run "MultipleInstances.exe" twice.
This proves that "Prevent Multiple Instances" is set and working, as you get an error.
3. Launch "SpamMultipleInstances.bat" batch file.
4. 10 instances of the game are launched without an error.
Expected behaviour: Only a single instance of the game allowed to be launched.
Actual behaviour: A lot of instances launched.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment