ConsciousActs
-
Posts
14 -
Joined
-
Last visited
ConsciousActs's Achievements
Newbie (1/11)
1
Reputation
-
Awesome, thanks Carlosan! I assumed it was something I was missing—I wasn't assuming that the font scaling was responsible for the entire UI scaling, so from a feedback standpoint, hopefully that's a useful data point. Could be solved either in documentation, or in changing the parameter name in preferences to "UI Display Scaling" or something more generalized than just fonts. Now back to getting back into 3DCoat! -
I've got a Dell S3220DGF and it's a 2560x1440 monitor. I just fired up 3DCoat for the first time in a long time, and noticed that my buttons/interface are quite large, and I'd rather free up some more screen real estate for the viewports... but can't find scaling options for the UI in the app anywhere, and the windows compatibility option changes are yielding no joy. Can a I get a little help/what am I missing?
-
I have sent an email—now can I get access to Mantis fixed for regular bug reporting purposes going forward? Also, suggestions for fixing auto-reporter if it's something on my end with that error? Contrary to the 'closed' status on this thread here: http://3dcoat.com/forum/index.php?showtopic=18729 this isn't resolved yet ;-)
-
Third crash this morning—I opened the file to try again and try to work-around: 1) duplicated the layer I'm trying to operate on. 2) converted layer to voxel representation 3) chose the vox extrude tool 4) made a single brush impression selection (so it'd be small) 5) Hit "apply" ... 6) Note bug information https://www.dropbox.com/s/iyhzr18tztvdlla/2016.1.9.3dCoatCrash3.txt?dl=0
-
I'm not sure attachments got attached, so dropbox links: https://www.dropbox.com/s/cdxcw27h9eauxpm/2016.1.9.3dCoatCrash.txt?dl=0 https://www.dropbox.com/s/1846xbc20rmkobw/2016.1.9.3dCoatCrash2.txt?dl=0
-
Had a second crash trying to use the voxlayer command—it memory-leaked and then crashed when it didn't complete the operation. Bug report output attached (since the auto-reporter isn't working).
-
I was attempting to apply the Vox Extrude tool after making a selection, the layer was in surface mode, but it was the only layer visible. There were several other layers but they were turned off. I was having some odd behavior with the auto-save previously where I would see the counter counting down and I would ctrl-s save, which would cause the count-down to disappear as it should but then it would re-appear and start counting where it left off before I saved, as though it wasn't recognizing my save attempt. Then, when I put my above note into the crash reporter and tried to send my crash I got this error: Fatal error: Cannot access empty property in /var/www/vhosts/3dcoat.com/httpdocs/typo3conf/ext/bug_report/pi1/class.tx_bugreport_pi1.php on line 107 So I've attached my crash output to this post as well as the above comments. Hope that helps fix things!
-
Ok, so here's an interesting problem... I want to do a clean install to go to v4.5 beta 12, and make sure none of my older stuff interferes. However when I open Windows7 add/remove programs, I get nada in the list. I know I have 4.1 and 4.5 beta 11 installed, and I had renamed my the 'my documents' directory for 4.1.x to "3D-CoatV4_Backup" prior to installing 4.5. I'd like to try totally cleaning out *all* of the different places that may have stuff installed to them, to *really* start fresh. Is this listed anywhere that I'm missing?
-
I'm in agreement with Palex with the invisible polygons in retopo being a problem- while the invert mirror trick works, is there any reason why the polygons shouldn't be visible regardless of which side of the mirror you draw on? -ConsciousActs
