{"action":"created","issue":{"url":"https://api.github.com/repos/morse-simulator/morse/issues/687","labels_url":"https://api.github.com/repos/morse-simulator/morse/issues/687/labels{/name}","comments_url":"https://api.github.com/repos/morse-simulator/morse/issues/687/comments","events_url":"https://api.github.com/repos/morse-simulator/morse/issues/687/events","html_url":"https://github.com/morse-simulator/morse/pull/687","id":126148000,"number":687,"title":"Faster than realtime","user":{"login":"adegroote","id":377715,"avatar_url":"https://avatars.githubusercontent.com/u/377715?v=3","gravatar_id":"","url":"https://api.github.com/users/adegroote","html_url":"https://github.com/adegroote","followers_url":"https://api.github.com/users/adegroote/followers","following_url":"https://api.github.com/users/adegroote/following{/other_user}","gists_url":"https://api.github.com/users/adegroote/gists{/gist_id}","starred_url":"https://api.github.com/users/adegroote/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adegroote/subscriptions","organizations_url":"https://api.github.com/users/adegroote/orgs","repos_url":"https://api.github.com/users/adegroote/repos","events_url":"https://api.github.com/users/adegroote/events{/privacy}","received_events_url":"https://api.github.com/users/adegroote/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":8,"created_at":"2016-01-12T10:31:46Z","updated_at":"2016-01-15T10:38:50Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/morse-simulator/morse/pulls/687","html_url":"https://github.com/morse-simulator/morse/pull/687","diff_url":"https://github.com/morse-simulator/morse/pull/687.diff","patch_url":"https://github.com/morse-simulator/morse/pull/687.patch"},"body":"It is the first attempt to handle #338. You need blender-current (and python 3.5) to test it.\r\n\r\nI still have doubt on the interface. \r\n\r\nset_time_scale for moment only changes time_scale, and not fps. fps in blender is really frame by real second. So it means that if you set the time_scale by two, you will get sensor information at 30Hz (simulated time). It is possible to automatically adjust fps to have frame by simulated second constant (but we may need to raise max_logic_step / max_physics_step), and we need to handle #683 too. I suppose it can raise problem too if we have a really low time_scale too (but who really need that).\r\n\r\nYour through ?"},"comment":{"url":"https://api.github.com/repos/morse-simulator/morse/issues/comments/171929785","html_url":"https://github.com/morse-simulator/morse/pull/687#issuecomment-171929785","issue_url":"https://api.github.com/repos/morse-simulator/morse/issues/687","id":171929785,"user":{"login":"adegroote","id":377715,"avatar_url":"https://avatars.githubusercontent.com/u/377715?v=3","gravatar_id":"","url":"https://api.github.com/users/adegroote","html_url":"https://github.com/adegroote","followers_url":"https://api.github.com/users/adegroote/followers","following_url":"https://api.github.com/users/adegroote/following{/other_user}","gists_url":"https://api.github.com/users/adegroote/gists{/gist_id}","starred_url":"https://api.github.com/users/adegroote/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/adegroote/subscriptions","organizations_url":"https://api.github.com/users/adegroote/orgs","repos_url":"https://api.github.com/users/adegroote/repos","events_url":"https://api.github.com/users/adegroote/events{/privacy}","received_events_url":"https://api.github.com/users/adegroote/received_events","type":"User","site_admin":false},"created_at":"2016-01-15T10:38:50Z","updated_at":"2016-01-15T10:38:50Z","body":"> Well, my first thought is that, if you slow down the time, then you slow down the time! Hence, you also slow down the sensors -> I would expect to receive less updates from the sensors. So, no adjustement of the FPS. I guess some may have different use cases, I would keep it as the default.\r\n\r\nThe current code makes automatic adjustment in d5d6af086da413c084f1a565deb9e866e3b80fbe. Otherwise, you will receive a lot more data, as fps must be understand by Blender as frame by real second. Slowing side is the easy side, accelerating one is more complex (you can reach easily computing resource limit). Moreover, going faster than real-time is often to test \"high-level\" \"long-term\" algorithm, so in some situation, you do not need to have sensor update at 60Hz (simulated-time) (so 300Hz real-time if you have x5 factor)."}}