jwiede
Advanced Member-
Posts
505 -
Joined
-
Last visited
Content Type
Forums
Calendar
Gallery
Everything posted by jwiede
-
Howdy, account says I should still receive updates through July, but though I see both my 2023 3DCoat licenses listed, I see no upgrade indication for 2024? As it was just announced today, will that be a future change (hopefully before July)? Or will my existing 2023 3DCoat licenses just continue to work for 2024 3DCoat releases? I'm just trying to understand what, if anything, I need to do to obtain licenses that will work for 2024 3DCoat releases. Thanks! -John W
-
That thread just links back to this thread, it doesn't contain the source code itself.
-
Can you put the code up in GitHub or some equivalent location? Otherwise, what license would apply, and how do we obtain the source code? I can't make any promises, but there's a fairly decent chance someone will finish the AppLink for LW2018.
-
The ergonomics are no worse than actual painting, if you think about it. Holding up a paintbrush while painting onto an easel can also get tiring.
-
Sorry, I searched for LeapMotion but the search didn't return any results, anyway I'll continue in the other thread.
-
Could we have voxel sculpting made interactive with LEAP?
jwiede replied to L'Ancien Regime's topic in Feature requests
Yeah, I'm interested in this also, as I've got my shiny new Leap as well. -
Now that LeapMotion is out, and the SDK available for dev/test, I was wondering when/if we might see support for the LeapMotion device in 3DCoat? It seems perfectly suited to sculpting and painting given its 3D work field, and ability to sense both PSR & angle of fingers/tools in use. I even looked briefly at the SDK, and was quite impressed how well thought-out it seemed to be, designed for easy integration into 3D apps of all kinds. Thanks! -John
-
V4 Stable version
jwiede replied to Andrew Shpagin's topic in New Releases, Bugs Reports & Development Discussion
Andrew, congrats and thanks (as always) for all the amazing work and effort you and the team put into v4, and 3DC in general. I purchased my upgrade the instant I saw v4 was available without hesitation (just as with v3)! If anything, the pricing almost seems low for everything added, thank you for keeping such an excellent tool so affordable. -
OpenCL/CUDA for Mac in v4?
jwiede replied to jwiede's topic in New Releases, Bugs Reports & Development Discussion
So, at least at time of V4 release, there is currently no intention of supporting either OpenCL or CUDA on Mac in 3DCoat yet? Oh well. Is 3DCoat Mac GPGPU-acceleration at least something planned to be addressed at some point during the V4 version cycle for Mac? -
3D-Coat 3.7 updates thread
jwiede replied to Andrew Shpagin's topic in New Releases, Bugs Reports & Development Discussion
Aye, same here, without question or hesitation. -
3D-Coat 3.7 updates thread
jwiede replied to Andrew Shpagin's topic in New Releases, Bugs Reports & Development Discussion
Thanks much, Andrew!! -
3D-Coat 3.7 updates thread
jwiede replied to Andrew Shpagin's topic in New Releases, Bugs Reports & Development Discussion
Actually I kind of like the approach AbnRanger is proposing: Call v3.7.whatever (pick a stable subrev, .18 or whatever) the "final v3" and then treat everything afterwards as various pre-releases of v4. It avoids the "two live branches" problem, and realistically, calling v3.7 "the end" for v3 is still eminently fair in terms of everything that's been added in v3 since initial release. BTW, any word on when .18 for Mac will show? If it's already been stated, my apologies, missed it. -
Andrew & co, Any word on whether Mac users can look forward to OpenCL/CUDA support for v4? Lack of GPU "acceleration" is the one remaining area where Mac is solidly behind Win & Linux in 3DC, and it'd sure be nice to see that addressed. Thanks!
-
3D-Coat 3.5 updates thread
jwiede replied to Andrew Shpagin's topic in New Releases, Bugs Reports & Development Discussion
Many thanks for the info, Andrew! -
3D-Coat 3.5 updates thread
jwiede replied to Andrew Shpagin's topic in New Releases, Bugs Reports & Development Discussion
Any sort of ETA on when we can expect an update for Mac? Been quite some time since Mac was two versions behind Win (and given problems with 25C on Mac, really more like three behind), starting to get a little bit concerned. -
3D-Coat 3.5 updates thread
jwiede replied to Andrew Shpagin's topic in New Releases, Bugs Reports & Development Discussion
Any idea how much longer we'll be waiting for the OSX version of 3.5.25? -
Posted this over in the regular update thread as well, but figured I'd ask here in case Mac folks are reading this instead of the other thread: Ever since the first 64-bit beta, I've been having a problem with 3DC. It gets into this state as if the alt key is constantly held down (and yes, I've checked sticky keys, and other prefs that might cause similar effect). It doesn't always happen right away, but once it gets into this state, I can't figure out any way to get it back out again. Clicking with alt held, etc. doesn't fix it. Once in this state, I can't draw, etc. because mouse-dn dragging just rotates the view, and so forth. Has anyone else run across this problem? If so, any workarounds? It seems "new" to 64-bit 3DC, but as I've been messing around with peripherals it could as easily be an incompatibility.
-
3D-Coat 3.5 updates thread
jwiede replied to Andrew Shpagin's topic in New Releases, Bugs Reports & Development Discussion
Many thanks! -
Actually, mine doesn't look nearly as corrupted as theirs (on OSX 10.6.7, 3.5.19a EN), so I see the OP's point. It looks like the localization isn't properly accounting for the width of labels for German (and/or they need to use abbreviations in the German localization instead of the full words). If that's the menu bar they're seeing, it IS a bug, and worth mentioning. I, too, would love to hear some status about the 64-bit Mac work, as it does sound like Mac users are about to be "left behind" by some of the new tools due to those features' resource demands. I'm a bit disappointed of late over the lack of apparent priority assigned to getting 64-bit Mac 3DC done. 3DCoat's done a great job of maintaining feature parity between Mac and Windows users to date, but without priority getting 64-bit Mac released, the lack of access to >32-bit RAM resources is creating a feature gap in practical usage. Even though the features are present, Mac users can't access enough RAM to get real work done with those features, and that's becoming a problem. Andrew, can someone there please at least provide regular status updates about the progress of the Mac 64-bit work? Without them, from this side it starts to feel like there may not BE any ongoing progress.