Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.4.X, 2019.2.X
Votes
0
Found in
2017.3.1p4
Issue ID
1076650
Regression
No
[IL2CPP] Using MaxRayInteractions value more than 0 doesn't work
To reproduce:
1. Open attached project "testcase.zip"
2. Open "testscene.unity" scene
3. Enter Play mode
4. Press on the cube on the button or on the top, observe as the cube changes color
5. Build for iOS device
6. Open the build through Xcode
7. Press on the bottom cube it changes color, pressing on the top cube nothing happens
Expected result: cube changes color when pressing either the top one or the bottom one
Actual result: the view that has a camera with MaxRayInteractions set to 1 or more does nothing when the cube is pressed
Reproduced on:
2017.4.0f1 2017.4.11f1 2018.2.8f1 2018.3.0b1
Device reproduced on:
iPhone 7 Plus iOS 11.1.1
Xiaomi Mi Note Pro, Adreno 430 GPU, OS 7.0 with IL2CPP, doesn't reproduce on Mono
Doesn't reproduce on:
Mac OS 10.13.5
Windows 10 machine
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Add comment