Will this issue be tackled before the 2.81 release? Or will this wait for manta-flow integration?

It seems to me that the "intern domain area" is not in sync with object used as domain. When I apply the rotation the simulation works but the "internal domain area" is respecting the global axis and adjusts its size to bound the object domain, acting like a bounding box...

In my tests here I just cleaned the cache and the new frame rate works as it should. What happens is if you cache rigidbody at 24fps and then change the frame rate to another value like 60fps the playback will use that cached frames at 24fps and playback that cache with the new 60fps, resulting in a faster playback only on that cached(at 24fps) section of the timeline. that's why you should clean your cache (just changing some physics values) when you change the frame rate of your project.
What could help here is if you change the fps value it could clean the cache for you... but I'm not sure if it "should" clean the cache...

Thanks for the fix, Bastien Montagne! It's working as always now.
I'm so glad! The blender support is amazing because of you guys.

I also tried the attached file with the 2.80 official release from the blender.org site and it works as expected:

I also tried with a build bot build from today and I have the same issue with objects also.
Note the red lines indicating that I'm in the local axis rotation mode but it not happening... They rotate in global.

Looks like you have a working build...
Here I have this result with 135°:

I tested here and there are no more particles missing BUT there is one setting that is not yet following the switch from emitter > hair > emitter. It's the "render as" dropdown in the particle render tab. It's "halo" when particles are "emitter" mode and it changes to "path" in "hair" mode but when you change back to "emitter" mode the "render as" remains as "path". It's not showing in the viewport as path because of this render type needs a cached particle system. You can confirm that by repeating the steps from the bug report but at the end just bake the simulation to see the "paths" in the viewport appearing. I think that this render type setting should follow the system default and change back to "halo" when the mode is switched back to "emitter".

Wow! This was the fastest fix I ever see! Thanks for the blazing fast response, I really appreciate! Thanks! Now I can continue my work.

Thanks, Sergey and dev team! God bless you all!

After some more tests I think I found where the bug is... When I disable the "Auto Smooth" option under mesh property panel the glitch is gone and everything works fine like in the workbench engine... I still don't understand it since I'm not a developer but I know that it's related with "auto smooth" option.

Yes, I can confirm, I built blender again after the "FIX commit" and it's working fine now. This bug is gone! On more for the list o vanished bugs! Thanks! It's resolved!

I see this problem with factory startup also...
Here is a simple .blend and a screenshot.

Same issue reported on T58892.
Ok, I'm not sure if I'm allowed to do this here... let me know...
I have tested this one and I found that to solve this you need to change particle type manually. When you change the particle type to hair the particle type is set to "path" on "render as" option in the render dropdown inside the particle system. You need to set the particles to halo again and they will show up in the viewport again.

Ok, I'm not sure if I'm allowed to do this here... let me know...
I have tested this one and I found that to solve this you need to change particle type manually. When you change the particle type to hair the particle type is set to "path" on "render as" option in the render dropdown inside the particle system. You need to set the particles to halo again and they will show up in the viewport again.

I have the same problem on Ubuntu 17.10, I was able to build without problems before the commit that upgrades numpy.
I also have this warning when building blender that was not present before some recent python related commits:

This is working now. On cycles and blender internal.
Tested on Linux.
Thanks!

In T51012#424012, @Germano Cavalcante (mano-wii) wrote:

Are you sure this worked before?
I have tested here and it seems like, it always worked as a point. (What is strange considering the Curve option)`
Maybe you are confusing with the Curve Guide type. No?

Hello!
I have a fresh installation of Ubunutu 15.04 and I tried to run the Install_deps.sh and it got 2 errors... Can you help me to understand this errors? Sorry if this is not the place for this...
This is the part of the terminal log. Everything before this part just run well.
I'm using the proprietary driver from AMD and I have a ATI card HD7750...

Wow!
How fast! Thank you, team!

Ok, Here is the file that I'm working with.
https://www.dropbox.com/s/f49451n1dkerjpa/Prensa_008.zip?dl=0

Sorry! Please, delete this bug report!
I was doing things wrong here, It's not a bug!

Thank you, Lukas! Thank you very much!