Jump to content
3DCoat Forums

Gary Dave

Advanced Member
  • Posts

    415
  • Joined

  • Last visited

Everything posted by Gary Dave

  1. Nice nice, I look forward to what you have to show.
  2. I think there's some mass confusion going on here. Kajet's end goal here is to just retopo over a high poly object he has made in Zbrush (original post). But he was having issues with the strokes tool not giving the expected results. Tony suggested he hide his sculpt so he can better see the polygons that have been created underneath it. Kajet couldn't do this however, because he's probably imported as a reference mesh and therefore his high poly model doesn't exist in the voxtree, this is why he's saying he can't hide his model. Carlosan has given the right answer though, but I wanted to make sure we're all aware what the intended goal is here. I think different terminology in other apps might have caused a little slip-up there! The window that Kajet needs in order to hide his reference mesh in the retopo room is "Windows > Popups > Paint Objects". and/or "Windows > Popups > Surface Materials" if he'd rather hide by UV's (I think that's what surface materials is anyway, to be honest I find the terminology confusing inside 3dc) Alternatively, Kajet, you could jump to the paint room, and hide the reference from there. Or, simply import your high poly mesh into the sculpt room as a surface object (without voxelisation) and then it will exist in the VoxTree,
  3. No I don't think the amount of poly's will be the issue, 3dc can handle millions of those things. As Tony said earlier though, sometimes the strokes tool can mess up a bit, I know I've had a lot of issues with it in the past while also having symmetry active.
  4. It looks like you've probably imported the model into the paint room (for per pixel painting or painting with ptex, this is why you can see it but it does not exist as a retopo object or as a voxtree object.
  5. In regards to this placing on brush issue, it was mentioned on the forums before (No idea where, sorry), I know this because I chimed in as it was affecting me too. I do remember it not affecting others who tried to re-create it, and tinkering with my brush settings didn't alleviate the issue. The only redeeming thing I do remember, is that starting a new project with a different mesh did not have any issues with the "On brush" feature. So, it was something in our work files, or something we'd done along the way that had caused it, but starting a new project with the exact same settings seemed to "fix" it.
  6. I like it, very tidy modelling.
  7. Using 4.5.19, neither of the results you guys are getting are repeatable by me. (tested in 32 and 64 dx and CUDA and OpenGL versions) If my mesh is outside the margins, I don't get zig zag cut offs because that's just where the bounds of the photoshop document are. So there's nothing outside of the bounds/margins, because that's the end of the document window. In your examples it looks like some major confusion about where margin lines are in 3dc and what the document size needs to be in photoshop? I don't suppose by chance that you're dumping this into a different monitor that has a different resolution? Just a shot in the dark, I'm not sure why it would matter, but it's all I can think of.
  8. Got a response from Andrew: Edit I would mark this as solved, but I'm still none the wiser as to why later stable releases haven't been released on Steam. If a user searches for the same thing in a few months time and finds this thread, the answer of 4.7 coming in 2 weeks isn't likely to help them! My guess is that it's just a manual process, and Steam releases will be available at some point after website releases.
  9. Good to see more shape coming to this, I was getting worried for a moment!
  10. I've had issues with using folders before in photoshop and 3dc getting a bit confused. I had thought they were fixed but I've just learnt to stay away from folders now unfortunately. Can't be of any use, but I did want to say that's some sick texture work you're doing.
  11. I like the modelling, though I'm a bit concerned that you're leaning toward futuristic sci-fi in your overall design.
  12. Ah okay, well that's good to know. obj must drop some sort of data, I would say that isn't the intended outcome though so hopefully someone can look into that.
  13. I think there's some confusion here. It doesn't mess up the scale. The pop-up window that asks if you want 3dc to remember the scale means it will remember the original scale of your model for later exports.
  14. I'm pretty sure it recognises your original scale, so it will keep it as the same scale of the original when you export it. At-least that's how I've been lead to believe it's supposed to work, never actually tested it. So you're okay to scale it up, just make sure you say "yes" when that window pops up and 3dc asks whether you want remember the scaling info.
  15. Yeah... I don't know about that, last time I opted in to the beta program via steam it downloaded a much, much older version. (like 4.0 something I think). I'll try to find the thread but I'm pretty sure it was suggested to not use that on steam, because it just isn't kept up to date. Not only that, but I'm not asking about a beta, the current beta is 39 I think? But the latest stable is 37. I would expect my steam version to be using the latest stable release.
  16. I see the latest stable release on the website is 4.5.37 but the Steam version is still 4.5.19. When can Steam users usually expect their software to update to the latest? Edit Probably should have put this in the "New Releases and Betas" section, my bad.
  17. Gary Dave

    Taxi

    Very cool, hope to see more soon!
  18. Very interesting use of the word "Vehicle", it's not wrong! Look forward to progress.
  19. Not sure if it's been mentioned or not yet, but is it worth holding off until the GTX 1080 or 1070 come out? Pretty beasty cards for quite a nice price range. The only other thing I'd echo in this thread is the extra HDD's, even relatively small projects in 3dc can stack up the GB's, especially if you're saving recursively (iterations/multiple files). I've gone with a 256(ish) SSD for OS and other bits and bobs, then another 512 SSD for current working files and important software installs, and then a 1TB high speed non-SSD as an archive of sorts, old work files and completed projects usually end up on there.
  20. Nice, I really like where this is going. It's like a submarine, but for the air! Can you give any information on how you achieved things like the netting wrapped around the balloon things?
  21. Good shapes, are you making use of things like Vox Hide + objectify hidden, and oval shaped cut off tool selections for that?
  22. Ah okay, I've read something similar elsewhere on the forums about the previous "which version do you want to run?" not being an option any more and it would just default to CUDA. Seems like an odd choice, and even stranger if non-CUDA versions are actually old versions. I personally steer clear of CUDA as I've noticed a lot more crashes compared to a regular 64bit DX, but I think this might just be an issue with my hardware, as CUDA is the wisest choice on paper, so you should be fine.
×
×
  • Create New...