Eric Cosky

  • Content count

  • Joined

  • Last visited

Community Reputation

7 Neutral

About Eric Cosky

  • Rank

Contact Methods

  • Website URL
  • ICQ

Profile Information

  • Gender
  1. Lack of dual monitor support is something I'd like to see addressed, even if it just means allowing windows to be positioned outside the main window instead of always being child windows. I think it would be tremendously useful if users were able to provide their own variation of fx/cg shader used by the paint room with a toggle to switch between the standard and custom shader. This would allow us to paint models that rendered the final texture data (color,specular,emissive,normal) in custom ways as needed by game development. This would mainly be useful for animated effects. The current architecture of supporting only color, specular, emissive and normal channels is a pretty big limitation as compared to Mudbox's more flexible channel support. It would be very helpful if we were able to define the texture channels we want, assign them to a UV set, and bind them to inputs of the display shader which would be customizable per scene (with a default setup that behaves as it does now).
  2. Thank you - I never wanted to bother asking for an upgraded file dialog but this has been a small annoyance in 3DC for quite a long time and I'll be glad to see this get updated.
  3. This is a very welcome change. I've been dealing with these artifacts for a long time without realizing the cause, always assumed it was my fault somehow. I also use 3DC primarily for painting low res game models made with another tool (Softimage) and I'm glad to see this fix show up.
  4. I can't speak for Andrew's plan for scripting, but as a programmer myself I will say that providing a C++ API could be the basis for adding support for any other language. It is also a lot easier to start with because you can generally just make functions that already exist within the application visible outside the app as opposed to building an intermediate layer that has to speak both languages and handle the transfer of data between both worlds. IMHO it makes a lot of sense to start with C++ and build support for other languages on top of that layer.
  5. Speaking of delay & lag, one of my biggest long-term complaints about 3DC is how often the app is unresponsive with little or no indication of what is going on or how long it might take to finish whatever operation I just triggered. This spans pretty much the entire app when any expensive operation is performed, I presume because the basic app framework has the UI processing done by the same thread doing all the heavy lifting. While some of these operations do have (pretty easy to not notice) indicators in the status bar, most commands don't. In terms of the quality of user experience, I think it is a pretty big deal to have the app window visibly grayed out by the OS because it isn't handling input events in a timely manner. Every single time I wonder, did it crash again? Should I wait longer? Will I be going to the task manager to kill it? It would be really nice to see this improved someday, but I do recognize that this would probably be a lot of work and may never happen.
  6. It would be really useful if Sketch had an option to use greyscale images as a bump map (with minimum/max thresholds) instead of just an on/off stencil so I could paint some elevation details in photoshop before importing it. Or perhaps there is another way to do this in 3DC already?
  7. What is the trick to making this work? I have a model with about 20 uvsets/materials in the UV room and I get a a huge number of images being exported. I don't see any options anywhere for merging them at export. This was an model imported for PPP, and as a result there is no retopo mesh (and incidentally why there are so many materials.. it seems to have made one for each Softimage cluster), maybe that is messing me up. I was hoping the "Export UV sets as tiles" was the feature, but toggling this seems to have no effect. Thanks for any info
  8. Andrew, can you please let us know if a crash that is submitted via crash handler + automated webform submission is sufficient for tracking, or is it better if we also create a Mantis report to make sure it isn't lost in the process somewhere? For example, this is the one I just sent in which seems legit; I can make a Mantis entry if necessary but I'd rather not make more bug tracking work for either of us if it isn't helpful. Thanks- Comments: Crashed after deleting object in paint room, returning to retopo and hitting apply symmetry. Bug report: Version:3D-COAT 4.00.BETA9C(CUDA)(DX64) Memory status: OK pointers: 62345 Video: NVIDIA GeForce GTX 560 Ti NVIDIA GeForce GTX 560 Ti nproc: 8 (1)object: (C:\\dev\\Shipyard\\main\\Apps\\SquadMiner\\Content\\3D\\SquadMinerXSI\\Scenes\\Actors\\FlareGun\\FlareGun_Assets\\FlareGun-crash.3b) vert: 0 poly: 0 rt:256x256 undo: (277) SMLC LPUS LPUS LPUS LPUS LPUS LPUS LPUS LPUS tool: RetopoTool NumMeshLoads: 1 Time since mesh loading: 4205 s VoxelTool: 41 RetopoTool: 1 UV_Tool: 1 41D20BDA d:\\tempbuild\\3d-coat\\uv_mapper.cpp line 1940 [+44], ClusteredMesh::ApplySymmetry+3738 4015D4F3 d:\\tempbuild\\3d-coat\\retopo.h line 21 [+0], RetopoTool::ApplyTopoSymm+35 400FEE39 d:\\tempbuild\\3d-coat\\simplewidgets.h line 537 [+17], wpcallback::call+537 41E0AF7D d:\\tempbuild\\3d-coat\\simplewidgets.cpp line 926 [+24], BaseWidget::CallCallbacks+621 41E21723 d:\\tempbuild\\3d-coat\\simplewidgets.cpp line 1518 [+21], Widgets::ProcessWindowsMessages+1171 4016F20B d:\\tempbuild\\3d-coat\\simplewidgets.cpp line 6460 [+10], IntfWidget1::OnButtonDown+219 41BC5540 d:\\tempbuild\\comms\\cwidget.cpp line 465 [+44], comms::cWidgets::HandleInputEvents+1424 416DA979 d:\\tempbuild\\main.cpp line 126 [+0], comms::cMain_OnRender+265 41BAEC69 d:\\tempbuild\\comms\\cwinmain.cpp line 607 [+0], cWinMain_OnRender+217 41BAEDEF d:\\tempbuild\\comms\\cwinmain.cpp line 1983 [+0], cWinMain_OneIterationOfMessageLoop+367 41BB120F d:\\tempbuild\\comms\\cwinmain.cpp line 2264 [+0], WinMain+4847 40434E17 f:\\dd\\vctools\\crt_bld\\self_64_amd64\\crt\\src\\crt0.c line 263 [+33], __tmainCRTStartup+391 7745652D line 0 [+0], BaseThreadInitThunk+13 7789C521 line 0 [+0], RtlUserThreadStart+33 7789C521 line 0 [+0], RtlUserThreadStart+33 General information: Exception code:C0000005 3D-COAT 4.00.BETA9C(CUDA)(DX64) Memory status before run: Memory load: 66 TotalPhys: 4293378048 AvailPhys: 55443456 TotalPageFile: 4289892352 AvailPageFile: 1390338048 TotalVirtual: 4294836224 AvailVirtual: 4117700608 Memory status after crash: Memory load: 70 TotalPhys: 4293378048 AvailPhys: 3811983360 TotalPageFile: 4289892352 AvailPageFile: 1726304256 TotalVirtual: 4294836224 AvailVirtual: 3241013248 AvailVirtual: 3241013248
  9. Yes, quite some time ago in fact which is why I never even considered these features to be a permanent part of V3. You're right though, naming the builds V4 beta would have made it more clear however I don't agree that the lack of clarity here is enough to justify giving freebies away to people who couldn't be bothered to read the manual. Andrew deserves our support, and if people want to get bent out of shape over this then I would personally consider that to be an unfortunate and unjustified overreaction. Not that my opinion matters at all here.. and it is just my opinion. I couldn't agree more.
  10. I would just like to quote version 3.7 of the 3DC manual, from November 2011: "24.0 Beta tools Edit->Preferences->Show beta tools. Beta tools are mostly intended to be in the next V4 but if you want you may enable them." While clearly people have different ideas about the meaning of "beta", and perhaps Andrew could have made his intentions more obvious with different messaging in the application itself, I don't think it's very fair for him to have to grant V4 features to V3 users just because of a misinterpretation that could have been cleared up by looking at the manual. Just my 2 cents. Edit: I suppose it could have helped to mention "beta features will be disabled when V4 comes out", but really folks what other programs have you ever seen that didn't disable public betas when the final version is released? It seems reasonable to give Andrew a pass on this even if you think it was an oversight considering all the stuff he has done to make 3DC and his open relationship with his customers what it is today.
  11. Andrew I think your current policy & plan regarding beta & disabling v4 features in v3 is perfectly fair & reasonable. Anyone familiar enough with 3DC to go in and turn on the beta checkbox, followed by the essential trips to the forums to figure out how to use the new features could only believe they were part of v3 if they are deliberately ignoring the obvious fact these are beta features for the next version. It is an almost universal fact that beta versions of significant software expire in order for very obvious reasons. A closed beta will not provide as much feedback as an open beta, and 3DC would only suffer as a result of the reduced feedback. If there is anything at all to be done to improve the communication of this - the need for which is questionable at best imho - change the label on the beta checkbox to say "Beta test features for the next version" and make a dialog that pops up when it's turned on that says "Beta features are a work in progress for the next version. Do not enable this in a production environment unless you are willing to adapt to unforeseen stability issues during the beta process and intend to purchase the upgrade because there may be backward compatibility issues. These features will be disabled when the next version is released.". IMHO anyone who thinks this policy is unreasonable is in fact the unreasonable one.
  12. Thanks for the update! I get the same error though, unfortunately.
  13. Good to know, thanks!
  14. Thank you for making the larger new icons+labels optional. As a 1080p display user the real estate of the big icons is not something I can afford, and I still prefer to use the text buttons. On a related note, it would sure be nice if the app's main menu were in the title bar like Photoshop CS6. The app's main titlebar is wasted space that I'd like to use if at all possible.
  15. Just have the original high res painted mesh visible in the paint room and use Merge with NM (per pixel) with your reduced mesh in the retopo room. This will cause the object in the retopo room to be copied into the paint room as an object, baking the texture sampled from the objects currently visible in the paint room in the process. The docs do a poor job of explaining this, but that seems to be how it works. I am pretty sure there other ways to bake textures in 3DC but I've never looked into it much, it was hard enough to figure out how to do just this much.. It's really hard to tell from the docs what is and isn't possible with respect to baking textures, it seems to be mentioned only in passing as if people only needed to be reminded of something they already knew how to do as opposed to it being a significant feature that warrants a detailed explanation of what is possible and what specifically to do to use it.