I just had a thought… something in common between my original paste/move event and this new changing layers event… I did something in the command window, did something else, then did something in it again… could the command prompt be doing this? I have my command prompt in window at the bottom of my screen, it’s easier for me to read with bifocals than the top of the screen… but it’s probably not a normal configuration since it’s not the default… I also have it this way on my laptop, but I didn’t bother on my wife’s computer. I wonder if somehow the command prompt in a window is causing the boing… wait a minute… it’s easy to test… just make the command prompt in a window on my wife’s computer… be right back…
Ah Ha! now my wife’s computer boinged!!
wait a minute… I’m going to dock my command window…
nope, now mine is nice and quiet…
Undock… Boing!
Docked… No Boing!
It’s something to do with doing something in the command window, then doing something out of the command window, then doing something back in it again… only if it’s in a floating window. That’s why when I use the move button instead of the move command it doesn’t happen, I’m not typing in the command window.
I also just tried something new… normally when I work, I will do something like click and select my default layer and then just start typing… but just for fun, I tried actually selecting the command window. and if I do that, I don’t get the sound… Strangely I don’t get the sound until I hit enter, so I type Move, no sound and my text is showing in the command window, but as soon as I hit enter I get it.
Anyway, on two computers I tried it on, docking the command window does not cause this issue, undocking it is required to make this happen.
this one I could reproduce, but not just with switching current layer – I can also do it by changing the layer of the plane & line in object props, or other such actions that shift focus from the command line mid-command
and I am also able now to reproduce your original issue by having the cmdline undocked, with sound scheme set to windows default, and I confirm that it is the “default beep” sound that is played, by changing it to something else
furthermore that I can make the behavior come & go in a given session (i.e. no need to restart rhino or anything), by undocking or docking the cmdline before repeating the steps, that using ctrl+insert or ctrl+v makes no difference, and that it is possible to switch sound scheme during the session, with different sounds for “default beep”, and the current scheme will be used
I’m glad there is an explanation. Moving the command line into a window was a recent change that I made, I have always had issues reading it, because it’s in the distance part of my prescription, and I finally decided to see if I could move it lower, so that’s why I never noticed this before.
Now that I changed my sound for “default beep” to something unique, these unexplained sounds from the command window become a lot more noticeable.
I’m relieved that it’s just the command window doing it, and not something like, “your geometry is corrupted… here’s the boing but we forgot the dialog box” when this happens if feels like there is a failure of some sort, but then it’s unexplained… so not something you want happening on a huge, complicated project. The sound itself does not bother me… It’s the not knowing why it was being produced that was really bothering me.
I tried docking the command window at the bottom of the screen and I’m not happy with any of the arrangements down there, it’s either the full width of the screen or if I put something next to it, that thing is too tall because it has to match the command window. Hopefully this can be fixed in an update because I really like my command prompt in a window.
however, with much of the UI being redone, it is also possible that this weird obscure behavior may simply go away, but I don’t have v8 on my machine that has speakers, so can’t check right now
I have V8, but it expired… it was a while ago I was messing with that. I think I’ll download it again and see how it works. It will be nice to see the options for docking the command prompt, and also to see if the floating command window has this issue.
Windows 10 (10.0.19044 SR0.0) or greater (Physical RAM: 64Gb)
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA Quadro M4000 (NVidia) Memory: 8GB, Driver date: 3-17-2022 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 512.15
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 3-17-2022
Driver Version: 30.0.15.1215
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 8 GB
Rhino plugins that do not ship with Rhino
C:\Program Files\SimLab\Plugins\SimLab VR from Rhino\SimLabVRPlugin.rhp “SimLab VR for Rhino”
C:\Users\james\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\EleFront\4.2.2\ElefrontProperties.rhp “ElefrontProperties” 1.0.0.0
Here is a sample file and instructions. It only happens under circumstances where you do something in the command window, leave the command window and go back in. for the sequences that produce this, it happens every time.
Also select a line and a plane that intersect, type intersect on the undocked command prompt, but don’t hit enter… then go to layers and change another layer to be the default, and hit enter (don’t select the command window… just hit enter)
additional info for cases 2 & 3, it makes no difference if I have other panels (obj props, layers, osnap) docked, floating, or not opened at all, neither whether I have rhino maximized
Type Distance – get some distance with mouse clicks
push duplicate Edge button
select some edges to duplicate
hit enter to duplicate edges
type move
hit enter
alert will play after hitting enter
Note, if you do not do some command in the command prompt before this entire sequence, it may not. it seems the command window needs to be either selected or used at some point before this will happen.