I am noticing some things with the Mac version that slow my workflow down. I use the command line mainly so perhaps the Mac version is just not suited for that type of workflow.
For example, if I use _ArrayPolar in R5 on Windows I can call the command with an Alias, type in the centre point and hit return, type in the number and hit enter, type in the angle and hit enter. All without having to navigate the cursor.
On the Mac once I call on the Alias I have to move my cursor to the parameter window to give the input field focus. Why does it not automatically get focus? Same thing appears to be with actions like creating a sphere etc. Why does that paramater window not automatically grab focus for the first input parameter?
Actions like changing an objects layer also require more work than on Windows. On windows I can simply double click on the layer I want to change to finish the action. On the Mac I have to select the layer and move the cursor to press select.
The action of changing a colour layer on the Mac allows you to double click the colour to select and finalise the action like R5 Windows……why is it different for changing a layer? I could give more examples but I think this highlights my point.
The thing I really miss the most in the Windows version is the Command line. The Command history window is useless to me on the Mac as it takes so long to scroll down to get the most recent actions. After modelling for a few hours it becomes ridiculous. Why does it not show the most recent actions? Is there a way to clear that Window once it gets too long to at least reduce the scrolling? I have not been able to find it.
Am I missing something here? Is there a reason why the Mac version is designed this way? Is there something I can do in my setup to change things to suit my workflow better?
in any case for the command thing, if you use the floating command option, it works great.
it’s different from the Windows command line, [I’m not familiar with it enough to compare …] but it’s really good and comfortable to work with. + it doesn’t take any screen space once the command ended.
it never loos focus, so whatever you’d type will bring out the command prompt, no matter where your cursor is.
As far as the layer panel, in the WIP it should be the same [or almost the] as on window… I think the Devs did a lot of work over there.
Hi @Akash , I am using R7 on the 3 month trial. At this stage it looks like I will go back to R5 on Windows with tSplines and look at this later once 8 is out and see if they have made changes that suit me.
Using the floating window for the command history on the Mac R7 still does not fix the issue of parameters not being able to be submitted from the command line. You have to click on the parameter windows to give it focus.
If the software knows it needs parameters entered why does it not give that input field the focus when it pops it up? Seems unnecessary for me to have to stop typing to move a cursor to click on it …to then go back to typing… I can just type all the way in R5 on Windows.
Also with the floating panel for Command History it still shows the very first commands of the session…you have to scroll down to get the most recent.
Glad to hear you like how the Mac version works for you. I guess they cannot cater for everyone. For me it is a step backwards and slower to how I currently work in R5 on windows.
The ui in 8 is completely changed and is very similar to windows
I don’t remember clearly anymore how things are in 7.
If you are now on a new Mac? Then the performance will be also disappointing on 7.
So Yes at this point in time it makes little sense to buy 7 just for having access to the WIP.
Hi @sochin Rhino not giving focus is not a bug I recall ever encountering on the Mac in Rhino 7
Can you pls run _SystemInfo in v7 and post back the results?
Apple macOS Version 13.4 (Build 22F66) (Physical RAM: 16Gb)
Rhino is running in Rosetta2 on Apple Silicon
Mac Model Identifier: Mac14,9
Language: en-AU (MacOS default)
Apple M2 Pro (OpenGL ver:4.1 Metal - 83.1)
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: Apple
Render version: 4.1
Shading Language: 4.10
Maximum Texture size: 16384 x 16384
Z-Buffer depth: n/a
Maximum Viewport size: 16384 x 16384
Total Video Memory: 10922 MB
Graphics: Apple M2 Pro
Displays: Unknown (255dpi 2x)
Graphics processors
Apple M2 Pro
Color LCD (1512 x 982 @ 120.00Hz)
Hi @kev.r ,
Definitely not happening for me here. I run the command _Sphere and unless I want the last saved value typing in the command line does nothing.
In the sphere, It’s asking for the Center point first , or any of the other options.
[you probably know that to choose an option you type the one letter marked with an under line , to make it active without the mouse]
Hi @Akash, yes I know that…I want to type in the Centre point co-ordinates. But the same focus issue is with ArrayPolar and other commands as well that I use regularly.
Anything I type in the command line does not go to that popup window…until I move my cursor to that popup window and click on it to give it focus…then go back to typing.
Thanks for trying to help. It appears others do not have this focus issue and/or prefer to use the command line less.
I have the option to work mainly in the command line in R5 Windows but not on R7 Mac. Will stay in Windows for now. My new mac is a nice paper weight
Yes for sure stay in 5. don’t buy 7 now… no point anyway, 8 is kind of just around the corner.
[In 8 you just type the numbers and it works correctly. ]
Noticed your “new paper weight” only has 16gb of memory… this is kind of not really enough anymore.
Luckily the M2 can use the fast ssd for extra ram very well . [ A couple of weeks ago I had rhino complaining out of memory issue [ because of a bug] It was at that point using close to 650GB 600+ was just rhino]
@Akash for the last 10 years or so I have been using R5 in emulation on the Mac in Parallels and I have only allocated 6gb of memory of the 16GB total to the Windows VM. In R5 on Windows it constantly tells you how much ram you have available…I have rarely had an issue. Only time I had it blow out was with Clayoo (TDM subD) which had a memory leak.
With R7 Mac even in Rosetta emulation I have had no issues for what I model with 16gb so will be fine for me. If apps/plugins have memory leaks then I would rather them fix that than give the app more ram…which with the new Macs is no longer upgradeable anyway. Going to miss the old MBP 15 inch once it is really done.
