Known issues so far:

• Missing function to retrieve persona
• IsPedArrested doesn't return true for player arrested peds

Known issues so far:

• Missing function to retrieve persona
• IsPedArrested doesn't return true for player arrested peds

Will we also be able to get access to the LSPD_First_Response.PoliceComputer - mainly to determine if it is in fact open?  computer.isShowing is mainly what I'd be after so we can also determine if we need to ignore input from our mods?  I'll stop begging for API features now.... :|

Will we also be able to get access to the LSPD_First_Response.PoliceComputer - mainly to determine if it is in fact open?  computer.isShowing is mainly what I'd be after so we can also determine if we need to ignore input from our mods?  I'll stop begging for API features now.... :|

I second that motion. (Pretty please?)

At least with my mod this below worked for me to detect if the computer was open...

I'm currently having issues with my PC so I can not double check atm, but if I remember correctly, it works.

PoliceComputer policeComputer = new PoliceComputer();
if (Game.IsKeyDown(Keys.T) && !policeComputer.IsShowing)

 

I don't see that property in the Object Browser, but when I tried that, I get this:

'IsShowing' is ambiguous because multiple kinds of members with this name exist in class 'LSPD_First_Response.PoliceComputer'.

Any word on PoliceComputer.IsShowing?

It doesn't appear in the object browser, and Visual Studio tells me that its ambiguous, as in the error in my last post.

Any word on PoliceComputer.IsShowing?

It doesn't appear in the object browser, and Visual Studio tells me that its ambiguous, as in the error in my last post.

It doesn't say it's ambiguous for me. Which version of VS are you using? I'm using VS 2015 Community.

VS 2013 Community...but I am programming in VB.NET. That could be it, haha. I may have to go back and convert ALL my code to C#...which I don't want to do. 

VS 2013 Community...but I am programming in VB.NET. That could be it, haha. I may have to go back and convert ALL my code to C#...which I don't want to do. 

It's either that or have the team change it. VB.NET isn't case-sensitive which is why it's saying it's ambiguous for you. I don't think there's any other workarounds, unfortunately.

It's either that or have the team change it. VB.NET isn't case-sensitive which is why it's saying it's ambiguous for you. I don't think there's any other workarounds, unfortunately.

Yup, you're right. I did some digging, and that is exactly it. Sigh.