ShawnDriscoll posted at 9:19AM Tue, 09 January 2018 - #4321920

When I export as OBJ from a modeler into Vue, I don't re-calc the polymesh. That will jam up any UV mapping. I never see black in my Vue renders. I must have a version that makes polygons double-sided, so normals are ignored pretty much.

Hi Shawn. I do think having Vue recalculate the mesh was a part of the problem. I didn’t have it do that when I imported the current objects and it seemed to work out okay. Barry unchecked “make double sided” in the “edit object” setting, then re-checked it while he examined it, and the textures appeared to lay out properly. So, it may have been something I was doing incorrectly after a bit of further investigation on my part. All of the normals are facing the right direction with this version as well as the previous time I tried importing the objects. Now I’m thinking, unless there’s a reason to do so, I just won’t have Vue do any re-calc on the polys and take care of any mesh density issues within 3DS. Funny thing is I had none of the same issues with previous object imports from 3DS.

At least no "404" error as of this evening...

TheBryster posted at 6:04PM Mon, 08 January 2018 - #4321866

Unless I'm mistaken there seems to be the same issue with the tip of the starboard wing too. While the first render appears mostly shades of blue, the artifacts in the following renders appear to be the same blue. Could this be a lighting problem? Without any textures at all, what does the model look like?

Hey, thanks for responding! Actually the blue part on the end of the starboard wingtip is part of the model that hasn't been textured yet. The blue color is a background I was using in PS while making the preliminary camouflage texture.

The values in the first render looked off likely because I had gamma cranked up too high in 3DS. I just posted it to demonstrate the textures for the model weren't tearing in 3DS, the program in which I created the model.

The artifacts are blue in the second and third renders because that's the blue background for the textures I was using in PS (which help me determine whether I have anything in the texture painting misaligned, or just plain off in the UV map). It's a preliminary texture, but I wanted to see how it would look in Vue and the results were what you saw in the above renders. I have no idea why an entire canopy frame, to which a texture map was applied, would be all black. Nor do I have any idea why there would be black artifacts elsewhere (e.g. the gun port).

Since then I've imported the model piece-by-piece to try to make educated guesses about what was happening. Some pieces (the fuselage, clear canopy glazing, cockpit tub, and exhaust/air brake petals) are imported .OBJ objects. I found that I should not use the slider to increase the mesh density (in the "edit object" field) in any amount as I believe that is what was possibly causing the tearing problem for the fuselage. In using that slider is Vue, I guess, increasing the number of polys in the object (similar to 3DS meshsmooth/turbosmooth)? If so that would, I suppose, explain some of the tearing.

I imported the canopy frame as an .OBJ object and was not at all able to correctly apply my texture to it. However, if that same part was imported as a .3ds object I could apply the texture to it just fine. Same for the horizontal stabilizers. The .OBJ object horizontal stabilizers had to be swapped for .3DS objects for them to look right. Why? I have no idea. Anyway, this is what it looked like in Vue yesterday evening after adjusting sunlight and ambient lighting a bit:

The texture seems to be okay now, but I've no idea why I'd have to import one format over another for the parts to look better or for their textures to appear properly.

scottl posted at 11:41PM Fri, 05 January 2018 - #4320998

Thx, wonder if they would answer an email, probably not. Merry Christmas :)

I've been in contact with E-on via Facebook messenger and support via email for the past week to skull-out a texture issue when I import an object from 3ds. They're answering on FB messenger and email.

Steve K. posted at 11:31PM Fri, 05 January 2018 - #4321702

wheatpenny posted at 8:37PM Fri, 05 January 2018 - #4321662

I had to reinstall my whole computer and now I can't activate my copy of Vue, so I'm back to using Carrara until they get their website fixed.

I'm the same way with a new computer. But when I try to logon to cornucopia3d or e-on software, I get an error about logging on to the (something), but not the "Down for a few hours" that I've been getting for weeks. So maybe they are trying to come back up.

About using Carrara, that is an example of "Don't throw me into that briar patch!"

I just tried getting on e-on's website and got this:

"http://www.e-onsoftware.net/404.html

Not Found !

You should use the main domain ending in .com

The webmaster"

I had typed e-onsoftware.com into the browser, not it came up as a .net domain instead. Weirdness! But, no front page that says they'll be back in a few hours.

They continue to be quite active on Facebook. They don't want to be down any more than anyone else because it's costing them money every day they're down. It's also ticking off people who have content they're trying to sell via Cornucopia, which is also down. They won't mention why the website is down, but they are assuring people that the issue will be corrected as soon as possible and I would imagine that would also mean extending deadlines for extending licenses, activations, etc.