TommyDee

That's not a good sign 😱

There is a common thread developing ? Thanks for the details!

How did you find that solution? And thanks for sharing.

My Win10 only has an onboard Intel GPU and it loaded fine. As a matter of fact, that is where I learned I even had a menu. Imagine being a first time (and long time) user and not ever knowing a menu was there. And by long time user I mean one that tried repeatedly to make Cura work for me. Once the menu conveniently showed up years later it was like "D'UH!"

Thanks... I too require performance. So far, the NVidia control panel did the trick. My default setting for the performance info is to let Windows decide. This needs to remain such for me.

Yep, that was it. Funny how NVidia didn't recognize Cura as a 3D App by default.

I finally got to confirm the settings. By default, my CAD-leaning Lenovo P70 running Windows 7 Pro didn't recognize Cura as a 3D app. Similar situation with an older Dell running a similar hardware configuration. The top bar menu simply does not show up, and mouse click positions are offset. I know this has been going on since V2.3 because that is when I gave up on this last time. My Win10 laptop just isn't equipped for Cura. Today I added Cura as a 3D app in the NVidia desktop. Left all the setting at default and restarted Cura. Now Cura is running on the NVidia card and the menu finally shows up. Thanks guys:

I finally got to confirm the settings. By default, my CAD-leaning Lenovo P70 running Windows 7 Pro didn't recognize Cura as a 3D app. Similar situation with an older Dell running a similar hardware configuration. The top bar menu simply does not show up, and mouse click positions are offset. I know this has been going on since V2.3 because that is when I gave up on this last time. My Win10 laptop just isn't equipped for Cura. Today I added Cura as a 3D app in the NVidia desktop. Left all the setting at default and restarted Cura. Now Cura is running on the NVidia card and the menu finally shows up.

...or visversa, yes. I haven't tried changing the default graphics for Cura. I think it defaulted to my certified NVidia driver. Updating NVidia drivers to non-certified driver risks my bread-n-butter apps. I'll see if I can force Cura to go to the win32gdu. Oh, and it is also Win7 pro. I'll get there one way or another.

There is hope for me too then with my Lenovo/NVidia.

I've posted the enhancement request at GetHub for an entry field validation. I'm perfectly fine with the micron level precision now that I know.

It is a matter of completeness in the UI. I have a pet peeve in in that direction coming from that ilk. Some people care about that 0.5mm. A 1,000 layers is an every day thing under fine settings. I could go on but it isn't worth the wasted bits in the cyber universe. Just leave it to say that it would be a fit-n-finish enhancement request.

I got it. Obviously I am trying to mimic a known profile. It does surprise me that I didn't get a warning when I entered 0.1925 as a layer thickness and it allowed the entry. A simple UI fix would make this clear up front. Where do we submit ongoing bug fixes and enhancements?

Bummer. That means the layer height field(s) should probably be limited to 3 digits as well. I wouldn't have known without dissecting the gcode output.

Something is really fighting me on this journey. Adding a mouse to the mix helps zooming with the scroll wheel. ...Once I got the lint out of the scroll wheel. But this laptop only has one USB port and running Cura means limited battery life! Looks like I need to buy a bluetooth mouse to get around in Cura and have the charger in place. ?