ID: 5aae9b5dfa2bd8da2a642d36
Server [Rockford/Build/Event]: Rockford
Map (if not default):
Description: When using the material tool the material doesnt look correct on the prop and then it starts spamming luas in console then it crashes you.
Bug observed since: Week also ago
Images/Screenshots:
Steps to Reproduce: Its random.
Thank you for your bug-report, Gamerpro2266!
It will be reviewed as soon as possible by our Developers.
Out of curiosity, have you attempted to use the render override tool on the prop to see if that fixes how the material appears? It won't fix the errors, but it might fix the visual effect.
You can't it crashes you after.
Does this happen on other servers/single player?
(Mar 8, 2018, 07:35 PM)Kvatch Wrote: [ -> ]Does this happen on other servers/single player?
Its not just me that has it a couple others.
As Gamerpro said I have also crashed during this error. However, I have had it happen to me when I spawned in a vehicle and applied the red/blue lighting vehicle supply to it.
I then put the vehicle away because I decided to go with a government vehicle instead. I spawned in the Ford Explorer and made it unmarked using one of the Photon presets that I have. After I was done, this particular string of errors started appearing in my console;
[ERROR]
1. unknown - [C]:-1
Error in hook Think: ???
[ERROR]
1. unknown - [C]:-1
Error in hook Tick: ???
[ERROR]
1. unknown - [C]:-1
Error in hook PreRender: ???
[ERROR]
1. unknown - [C]:-1
Error in hook PostDrawTranslucentRenderables: ???
I didn't notice the errors until I figured out my Photon stopped working. I always try out the lighting and siren(s) before I start driving. The siren still worked, but the lighting had stopped working.
I decided to put the Ford Explorer away as my thoughts where the Explorer might've been causing the Photon error(s) and took my Chevrolet Tahoe out. When I tried to turn on my lighting on that vehicle too, it still didn't work and my console started flooding with the aforementioned error string following up with a crash.
It happened again today when using /note maybe the issue.
So basically this is an issue that LL cannot solve, at least what i've heard. If you crashed, upload your crash logs to facepunch.