Jump to content
3DCoat Forums

ScoobyDoofus

Member
  • Posts

    20
  • Joined

  • Last visited

Everything posted by ScoobyDoofus

  1. So I got in touch with Andrew and suppport. I was asked to send a log-file after a crash, which I did. I also discovered that the problem ONLY OCCURS when I move the application to my 2nd monitor (My Cintiq) and close it while on that screen. Any attempts to relaunch the app after that are met with a crash/stall. However, I can move the app to the Cintiq, work all day, then move the app back to my primary monitor, save my document, close it, and it'll relaunch with no issue at all. Very strange. Still looking for a resolution to this that isn't the above-mentioned work-around. Thank you!
  2. Ok. Just tried, and same result. I used the provided community license file from the linked thread. Still crashes at launch after 1st run to activate. I just uninstalled, rolled back to 2022.33, same issue.
  3. I have a 100% reproduceable bug where when I launch 2022.47, it will just completely hang at launch. No error message or other dialog. The splash/loading screen shows and an all white or all black app window. It'll stay like this forever if you don't end-task. IF you delete the entire 3dCoat 2022 folder from ../Documents, it'll run, and ask to be licensed/authorized again. If you DO authorize it, either with a local .license file or by entering your login credentials, it'll appear to authorize...and then if you close and re-launch it, its back to crashing every time. Even if you leave it in demo mode, the 2nd time you launch the app, it'll crash. The NEXT time (3rd time) it will launch a dialog, noting the last launch was unsuccessful and giving some troubleshooting tips. I've tried all these, to the best of my ability and knowledge. No success yet. I am running 3DCoat as administrator. Up-to-date Win 10 on 10th Gen Intel 10850k w/ Nvidia 3090 and latest drivers (although this crash has persisted for some time, and over a few versions). I am not using OneDrive, or SkyDrive or GoogleDrive or have them running currently. I am a long-time 3dCoat user, and having it broken is a bit tough as I use it regularly in production and need it for my current project.
  4. I also have this issue, and can't get anything usable out of 3D Coat. Its primary function in my pipeline is retopo, and now it is useless for that. It crashes with export, it crashes with AppLinks, everything. It won't export an object period. PLEASE look into this ASAP. I have clients waiting for assets, and this "beta" version is what is posted in both your regular release AND beta portions of the site.
  5. @PolyHertz Yeah man! I still use it and just upgraded to 3DS 2021 + Latest 3D Coat. Thanks for all your efforts on this so far!
  6. Currently, in the paint room, if a Paint Object is locked or hidden, it will still contribute to an AO bake. Locked items receive no lighting. The behavior I'd prefer is if an object is hidden during the bake, it should neither contribute nor receive any lighting info. (the new feature) If it is locked, but still visible, it should contribute, but not receive any lighting info.(The current status) When working on modular character systems, where the accessories need to take AO from the base-body, but not contribute to it, this would be very useful. Outside of deleting the paint objects, there is no method I know of to exclude an item from contributing to the AO calculation.
  7. Hey, thanks for the reply! Much appreciated. I'm going to give that a shot this afternoon. 3DC is really a great bit of software with a very deep feature set. I can't help but think though that at this stage, its got enough features for the moment, and some further work should be done on streamlining and usability cleanup.
  8. So, I usually use 3D Coat both at home and at work for retopolization and at least beginning my UV's. However...when I want to go from the retopo room to the UV room, the newly made mesh doesn't carry over. I realize I can establish seams, and perform a majority of the UV functions in the retopo room, but not 100% of them are available, and its confusing sometimes which export function will drop out a model that uses these UV's or how to "apply" the uv edits I've made to the mesh. As it stands now, I end up exporting my new model as an obj, relaunching 3D Coat and importing that model right back into the UV room and completing it that way. I really want to just have a button in the retopo room that is just "Ok, I'm done with my topology, I want to UV now" I see the ideal workflow in 3DC as being Vox Sculpt->retopo->UV->texture paint->render. I imagine that just having a linear workflow, albeit one that you can import data generated elsewhere at any stage, and continue on that path to completion. I'm sure I'm just missing something. Any help?
  9. Just still fiddling with some busts. Did this guy over the last 2-3 evenings. Textures are photo sourced, sculpt is from scratch(no refs). I'm shooting for something stylistically similar to the Mass Effect series. 1024 textures (diffuse, normal, spec) and nearly 3k tris for just the head. **Thanks and credit again to Cman2k for the eyeballs+shader which I'm using here. Strong critiques or comments always welcome! I'm aware that the pores are a bit jacked. They will be corrected.
  10. Previously Caps Lock would hid the cursor, but this is no longer the case. Is this feature still present, and if so, what is the new shortcut or where is the menu item? Thanks
  11. I did thanks. I've done a bunch of work in 3DC previously mostly Voxel doodles, painting a diffuse texture here or there and a little retopo. I'd tried to do this once previously, but had issues with the retopo & UV sections that I had to drop out to Silo. This time I was able to go A-Z. I was actually thinking about doing a video of the process w/ VO once I got stronger handle on it.
  12. Just a quick test in 3D Coat to do a normal mapped asset start to finish without ever leaving the application. Sculpt, retopo, UV's + normal & occlusion bake, then texture paint. Obviously its unfinished, but as a proof of concept on the workflow for me it served its purpose.
  13. I've got a bug where when I launch 3D Coat and hit the voxel mode button it claims my layer is "invisible" and I cannot sculpt on it (or see anything). All voxel models are invisible. Is this a setting or config or driver error? It worked fine on my previous OS XP pro SP3 install, but after upgrading to my new machine, it doesnt work. If I boot into Windows 7 64 bit on the same machine.....it works fine.
×
×
  • Create New...