Anyone ever seen this before? Try entering a distance for the offset. I doesn't seem to work. I've never seen this before, and I can't even reproduce it. But this file seems to be broken.
I had the same issue.
Make sure the box for 'use shaded preview' in system options-performance IS checked.
That fixed it for me.
this works for me on my 2013 version
Odd. I tried it on a couple of other computers here, and it is greyed out on them as well. However, if I reselect offset on them, then a value can be entered. Just not on my computer. All have the same version of SW, so it is computer specific. Hmmm...
Ok. Removed the registry entry for SW, (basically started with default install), and tried again. Now it works. Put the registry entry back, and it doesn't work. Something in my settings perhaps.
Definitely a settings issue. Use copy settings wizard to put my settings on other computers, and the problem follows my settings. Now, which setting is it?
I hope to see an answer to this also. I "upgraded" (always a dubious term) to 2013 a couple of weeks ago, and this morning was the first time I tried to enter an offset for an extrude.
BTW, isn't it time to rotate another photo onto the signin page for these forums? I'm getting awfully sick of that smug twerp with the loosened tie and hipster glasses.
I'm assuming that you also couldn't enter an offset. I still haven't figured out which setting has this messed up.
That's correct. Sorry I wasn't more clear.
No worries. When I have a little time, I'll try to figure this out. Until then, some files just don't work. BTW, I've upgraded to SP4.0 and the problem persists.
Does SP5 resolve this issue? We have just started using SW2013 SP4 and this is a HUGE issue. I find myself having to work around this a few times a day, and it is slowing me down. If someone has resolved this please let me know.
It's still there in SP5. I never did figure out what is causing this. Maybe it'll be fixed in 2014.
The Copy Settings Wizard does more than just copy the adjustable settings in your options menu. I may be wrong, but I believe it copies your entire registry settings (or at least a portion of it). So, if resetting your registry fixed the problem, then you may be stuck with doing that and manually adjusting your system options to get everything set back up correctly.
Once you have everything set up correctly, you can save a new Copy Settings Wizard file. You should be able to install this file on everyone elses machine to correct the error.
I have found that using the Copy Settings Wizard when transferring between versions can sometimes cause these type of odd errors to occur. When upgrading from 2012 to 2013, I was unable to use the new View Selector cube as the icon was removed from my view menu by the CSW file. After upgrading from 2013 to 2014, trying to access the Messages/Errors/Warnings tab in the System Options would cause SW to lock up until I reset my registry.
Yeah, I know that there is a lot of cruft kept in there. I could go on a long rant regarding the lack of intellegence shown in the decision to put all settings for all programs in one file. Pure stupidity.
I'll have to reset and start over one of these days, but as it entails a lot more than just resetting system options, (macros, hotkeys, menus, etc), it'll have to wait a bit.
You can actually try reusing your CSW file to import everything but the System Settings.
When I had the problems I mentioned earlier, I was able to bring in my menus, toolbars and keyboard shortcuts without causing problems. I just had to manually adjust the system settings.
Yes, I could restore only some settings and maybe find the problem in the 15 possible iterations. Might still have to reset everything. If it doesn't require resetting everything, it would probably save some time. I'll have to try it and see. Thanks for the suggestion.
It's working for me in SP5. I don't recall when it came back, sorry. I've done a couple of registry resets for other problems; maybe that had something to do with it.
Wow. That actually fixed it. I'd never have guessed that that would be the issue. I've had this issue periodically, and could never get it fixed.
Thanks a lot for the fix.
It still a bug so can you get it over to your VAR and into the SR system.
Retrieving data ...