{"action":"opened","issue":{"url":"https://api.github.com/repos/kami-/hull3/issues/59","labels_url":"https://api.github.com/repos/kami-/hull3/issues/59/labels{/name}","comments_url":"https://api.github.com/repos/kami-/hull3/issues/59/comments","events_url":"https://api.github.com/repos/kami-/hull3/issues/59/events","html_url":"https://github.com/kami-/hull3/issues/59","id":104857550,"number":59,"title":"disableRemoteSensors performance review","user":{"login":"Cyruz143","id":7225500,"avatar_url":"https://avatars.githubusercontent.com/u/7225500?v=3","gravatar_id":"","url":"https://api.github.com/users/Cyruz143","html_url":"https://github.com/Cyruz143","followers_url":"https://api.github.com/users/Cyruz143/followers","following_url":"https://api.github.com/users/Cyruz143/following{/other_user}","gists_url":"https://api.github.com/users/Cyruz143/gists{/gist_id}","starred_url":"https://api.github.com/users/Cyruz143/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Cyruz143/subscriptions","organizations_url":"https://api.github.com/users/Cyruz143/orgs","repos_url":"https://api.github.com/users/Cyruz143/repos","events_url":"https://api.github.com/users/Cyruz143/events{/privacy}","received_events_url":"https://api.github.com/users/Cyruz143/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-04T09:30:49Z","updated_at":"2015-09-04T09:30:49Z","closed_at":null,"body":"BI Post:\r\n```\r\nThere are two new commands - disableRemoteSensors bool and bool = getRemoteSensorsDisabled\r\n\r\nwhat are they good for:\r\n- each unit needs many raycasts to determine whom it can see (this takes a lot of CPU time)\r\n- most MP players do not really need the information if player #42 can see player #67\r\n\r\nSo this command will disable raycasts for remote (not local) unit that is in a group, that doesn't have any local units (you will not compute any raycasts for 85 remaining player)\r\nand hopefully saves some CPU time.\r\n \r\n- it will break knowsAbout script command (will not be updated), reveal should still work\r\n- commands are local and can be used for both client or server\r\n- state will be reseted when mission ends\r\n```\r\n\r\nRequirements:\r\nYou need perf client for this to work currently, might be worth kicking a few select people to update to it for testing purposes.\r\n\r\nImpact:\r\nNone that I can see in terms of negatives, we don't use ```knowsAbout``` in admiral anywhere I believe. Kami, whats the best way to implement this, for short term can probably get away with sticking something in the mission init:\r\n\r\n```c++\r\nif (hasInterface) then {\r\n    disableRemoteSensors true;\r\n    };\r\n```"}}