awnold
-
Posts
89 -
Joined
-
Last visited
Content Type
Forums
Calendar
Gallery
Posts posted by awnold
-
-
he application failed to initialize properly (*********) . Click on OK to terminate the application
My apologies on this is the error, but those numbers are wrong, tried to get a screenshot of it this time but there are no resources available when this happens. Anyways take it for what it is. might just wana ignore it Andrew.
-
I haven't had any problems like that and I've used v3 build 75 already for more then a 5 hour sitting.
yea but are you using pixel paint for more than 2 hours at a time doing painting like brush strokes? if im the only one then problem solved..
Its happened like clockwork since v67 -
v75 . Andrew I still get this error, about once per two hours. It happens when pixel painting, just normal paint strokes, 3dc will hang, cpu will be maxed out at 50%, internet will go down. when I go to manually close the application I get this error:
"The application failed to initialize properly (0xc0000135) . Click on OK to terminate the application"
Just wanted to give you a heads up. I could say I can predict it happening once every 2 hours of pixel painting. (lots of successive strokes). However its impossible to predict.
-
V 72 re-uploaded - view unshaded issue fixed.
working great thanks!
-
Excuse, I have set this limitation months ago and it was almost forgotten. I changed time limitiation several alphas ago.
Just download V71 or wait for 72. I will update to V72 today. Unsghaded model will look well there. If you need it just now, I can upload it now.
Every alpha has some time limitation that is moved forward sometimes. V72 will work until the end of May.
hey thanks Andrew, this makes it much easier to really test the beta. Thanks again! Oh and as far as "view unshaded" still not working here. just imported the cube for per pixel painting, hit view low poly model, then view unshaded model and this is the result. perhaps this is a video card issue? 8600gts latest drivers.
Oh and I like how preferences and layout are now saved.
Thanks!
-
OK I dont understand this at all. Why, when I have a valid license is this expiring? All this means to me is I cant do any work today since im using v67, since the view unshaded model has been broken since then.. please change this policy this makes it very hard on people who are putting their time into beta testing this program. I mean im 90% into a project and now I cant finish until either A) this issue is fixed, which I have asked about for weeks, 2) I purchase V3, while tempting, the real value is the time put into beta testing a program that (like the bug found 2 weeks ago) crashes the computer every 30 min and using the program anyways.
Thanks
-
All the color layers? sure, just -> Export all layers color (saves to layered psd)
then on the pixel paint one -> Import layers color.
should work..
-
I've been wondering if there will be any way to convert the microvertex textures to DP. That could be useful for older projects
sorry is this answer is retarded but just save the texture as high res as you can get. I think thats the best you can do.. then obviously load model back in for pixel painting and load the texture. I guess this assumes you UVed the model, perhaps that is what you are talking about..
-
This one is still alive kicking:
http://www.3d-coat.com/forum/index.php?sho...amp;#entry16797
thus, still using v67
-
when you activate "view unshaded model" turn "view lowpoly model" on .
(6 on keybrd)
your saying it works for you then, 'view unshaded model' with 'view low-poly model' on?
that has not worked here since v67
-
Andrew, im sure this is on your long to do list but view -> view unshaded model is still transparent here. cant use either 68 or 69.
However, thanks for the update!
-
Out of curiosity, does anyone have any problems with their middle mouse button on their stylus (wacom)? It only does this to me on Vista, but when I'm using 3DC, I use the middle mouse button to pan but when I let go to stop it seems that even though I let go, it is still panning like i"m holding it down. Unfortunately I am not holding it down though and I can't figure out how to solve the issue.
not sure about this but I put middle mouse on the stylus eraser, and I use the button up and down on the pen to increase/decrease the pens radius, works like a charm. So when I want to pan I just turn the stylus upside down and hold alt.
-
Hey Andrew thanks for the fixes of my submitted bugs!
One new bug, my favorite mode for painting is 'view unshaded model'. This mode comes up as transparent. (no texture at all)
Also, these bugs are still alive and kicking:
http://www.3d-coat.com/forum/index.php?s=&...ost&p=16488
http://www.3d-coat.com/forum/index.php?sho...amp;#entry16584
Also, the bug discussed here:
http://www.3d-coat.com/forum/index.php?s=&...ost&p=16450
does not happen like that any more and what does happen (the freeze) is much less frequent, once every four hours or so. I have not tried out v68 for long enough yet, but it might be completely gone now, will keep ya updated.
Thanks for the fixes!
-
Bug found
import for per pixel painting
get the cube (or whatever)
at this point you can paint on the cube in both the viewport and the texture editor.
save file
open file
you can no longer paint in the texture editor, only the viewport. (sometimes its so you can no longer paint in the viewport just the texture editor)
-
Andrew any chance you can squash another bug? When painting in depth in DP mode (on the normal map) and hitting Shift (to smooth) it screws everything up (you will see, you cant paint depth in this area any more).
Thanks!!
-
This is a strange little bug, and not even sure whats happening (this is also with microvertex paint)
1) open the obj cube for for per-pixel painting
2) take a fully saturated red and put the brush transparency to 50%
3) paint on the left hand side like I did here
4) then put the transparency to 100% and paint on the right side
5) ok then change the color to a fully saturated turquoise
6) change the brush back to 50% transparency.
7) paint over the red on the left (keep stroking on top of the red paint to 'build up color'. you can see, you will never be able to build up a saturated color no matter how many strokes you do on top of one another.
8.) ok now move to the red on the right and do the same thing, here you can build up the full saturation, if you do repeated strokes, when painting on top of the fully saturated red.
Ok, im not sure if this is a bug, but its very hard to understand this functionality. I was painting and this really confused me. Now once your model is fully saturated you never see this again. But make a new layer and this weirdness comes back. its very confusing. I hope you can make sense of this.
Thanks!
Oh, btw, I thought I had seen the last of the crashing because the color selector bug is definitely fixed. Its still crashing, however much less often it seems. And there is no bug report (because everything shuts down) and really nothing special that triggers it...
-
Actually, I agree partially. I like the presets we have, but I'd prefer a custom texture resolution as well. So we could go higher (if need be) then 8x and lower then 256. But that's just me.
no I got this wrong (thus deleted my post) andrew is already ahead of us, on 'import for per pixel paint' you can go as low as 64x64 and as high as 8192x8192. (i have no reason to go higher but other might) and hes currently working on changing the texture res on the fly..
-
another reproducible bug. there is something else wrong with selecting the color under the cursor 'V' (besides the lag I described above) if you use V to select a color, you can not undo past that point. So paint a stroke, use V to select a color, paint a stroke, the farthest back you can go with undo is the stroke after 'V'. Since I use V and undo a ton, I would not be surprised if these bugs were related to the crashing..
-
It is important to find and fix this issue. Please tell what do you usually do when it freezes (stokes, saving,...). Also, if this issue is regullar please make one test. Go to options and turn off "Use multicore optimisation". If it will help and 3DC will not freeze for a long time, go to options and turn it agan (on next session). Check if it will freeze again. I need to understand if it is multithreading related.
turning off muti-core optimization didnt fix it. I am painting, and it starts slowing (for a 1 second) then crash. Also, I only have 7 gigs a free space on my C: drive, perhaps its running out of virtual memory.. who knows I will clear up some space and see if that has any effect. I did manage to get a screenshot this time of some of the errors..
although this might be related to a problem easy to reproduce.
open the cube model for per pixel painting
start painting, hold down V and start sampling the underlying color, paint some more, more sampling (really hold down V) go back to painting, go back to sampling color V.. repeat quickly for about 2 min, really hold down V.. eventually the color selecting will grind to a halt. you have to hold the V down in an area for about 3-5 seconds for it to pick the color underneath. after this happens, you need to save and reopen to continue to work on the file. this might be related to the above problem, who knows... (they are not really related but the program grinds to a halt in both of them)
-
not sure if this is too vague to help you Andrew, but I still freeze, about 2 times an hour when doing DP. I do quick strokes in succession, which probably taxes the system, but who knows. What happens is this, the program will freeze, the CPU will be pegged at 50 percent.. now the interesting stuff. I cant open any program, and not only that all my disk drives show up as zero bytes. skype has an IO error and crashes. sometimes I can wait 3-5 minutes and it comes back, sometimes, like this last time, it freezes for 10 minutes and I have to kill it. I cant take a screenshot during this time, nothing works, even the system manager gives an error if I try to start it. This might just be too vague, but its the best explanation I can do.. hope this helps.
-
I had to post this, for a 'in the field' comparison between the old micro vertex paint and the new one before I colored it over. Here I think the difference is clear, the old paint is blocky, chunky does not blend well, its no per pixel paint. While the new per pixel paint is sharp, blends well and feels just like Photoshop. A picture is worth a thousand words so here it is. and as of v66 its workable (still need to save and reload every 10 min because of a bug that I will call the 'color picker bug' where holding down V will eventually lag out), other than that, its working great..... thanks Andrew!
-
Updated to V66 (Win & OSX)
Changes:
- correct undo/redo
- correct layer moving up/down and mering,correct work of all actions under RMB in layers palette (but topo symmetry)
- correct displacement import/export
- fixed critical save bug (3B file from DP mode was corrupted sometimes)
well it seems like you already squashed this one, but might as well post this while v66 is downloading. I didnt notice this was happening, but all the 'corrupted' files, or more appropriately, files which did not store the painting texture, are half size the normal ones. (arrow pointing to files where there is no texture data saved, and model comes in blank)
also you might get a bug report about a crash on save with v66 (what was happening is that ran out of disk space) saving a new file every 5 min will do that to ya! right now v66 is most likely working properly.
-
"Nice one awnold it sure looks like it's working pretty well so far."
to be fair, this was painted with the 'old' paint tools, haha, which really work great for low poly painting, not as good as the 'ultimate' solution- per pixel, but pretty darn good. Yup, just switched over and started to continue with per-pixel and il continue to report issues like these:
65 version
1) when holding down V (picking the color under the cursor) there is a good amount of lag (found how to reproduce this, just hold down V until it lags up, after that happens, it will always be lagged. only way to fix this is to save and reopen. if you are having hard time reproducing this just do a couple strokes hold down V and move the mouse till it lags. If that doesnt work, do a couple more strokes and repeat, should be able to get it to lag.)
2) also, after painting for about 10 min or so, the the V lags like above. just normal color selecting and painting over 10 min will cause it to happen, i have to save and reopen to fix.
3) after painting, then saved, then opened, all painting is gone. (not sure about this one either, some times it happens sometimes its fine)
4) this has happened 4 times in the last, well about 6 hours. While normal painting, the program freezes. When this happens I cant open ANY program whatsoever. I cant even open system manager, ie, wordpad, nothing. all have errors, (tried to take a screenshot but that does not work either) the program is using 50 percent of CPU when this happens and will stay like this indefinitely.
Thanks!
p.s. after using the old paint (micro vertex) and the new method (per pixel) the difference is incredible. It feels very similar to photoshop but its right on the model. In fact, once the bugs are hammered out im not sure what photoshop would have on it.. just incredible...
-
WOW it works!!!! I wouldnt believe it unless I saw it, how one man can program like this is beyond me... How did you pull off voxel scuplt and a working per pixel paint within months!!!?? gota be your faith and determiniation. You said you were gona do it, doing it is another issue.. amazing Thanks!
incredible program
in General 3DCoat
Posted
Hey been using 3dcoat recently to automatically make UVs, non-organic stuff, after using it in the past for pixel painting and seeing everything else this app can do im just really amazed that anyone could make this program, thanks Andrew for this incredible work. Its just mind blowing. I mean many of the features of 3dc are not even industry standard, just invented. incredible..