Archangel35757

Configure one and see: http://www.avadirect.com/custom-gaming-laptops

So what internet browsers (for older Android) do you support besides Chrome and Firefox?

I just bought a 17" gaming laptop from AVA Direct (best prices I could find)... and I decked it out with upgrades to be a graphics workstation. Check out their laptop options and customize it for what you want.

Quick Update: So I haven't made the progress I would have liked... ...but I have the Max2013 C++ project updated as dotXSI 3.0 v1.9 Beta and I have the export dialog updated with all of the new vertex normal export options. I also have the class methods updated so that all the new vertex normal methods are there at least in skeleton form (...and both x86 and x64 projects compile successfully). All I need to do now is write the five new methods (and correct the original two...) -- and then beta test it with @@DT85's help. Hopefully by the latter part of next week (I have to travel for work the first part of the week) I'll have a plugin for DT85 to test. EDIT: Once I get the Max 2013 exporter working properly... I will apply the changes/corrections and update all exporter plugins for Max6 thru Max2016 to v1.9.

Like @@mrwonko said, in the GLM format a vert can have only one UV texture coordinate... if you split the mesh along UV seams inside 3dsMax before exporting... then Carcass should not add any new verts along the UV seams. I think only the 3dsMax exporter needs fixing.

According to @@minilogoguy18 Carcass already unifies the normals along the UV seams where it inserts duplicate verts (per @@mrwonko)... so I think that all that needs to happen is for me to fix the vertex normals exporting in the dotXSI exporter. No -smooth switch needed. I'll get crackin' on this tomorrow and hopefully will have a beta v1.9 for you to test this weekend.

Oh... Consider This Request Efficacious Ensiform

So there is no "fix" for that since it's inherent in the GLM format. Best you can do is ensure the normals at that UV boundary are identical. Correct?

So @@minilogoguy18 did the above test in Softimage... ...why would Carcass split the mesh along UV seams? @@DT85, @@Psyk0Sith, @@Xycaleth? ??

It is just one of carcass' command switches like (-smooth).

@@minilogoguy18 - What happens if you use the -losedupverts switch?

Your browser software transmitted the following HTTP headers URL: http://xhaus.com/headers Request parameterValueRequested URI/headersRequest MethodGETRemote IP Address<REDACTED>Remote IP Port45035Protocol versionHTTP/1.1HTTP Header*ValueAcceptapplication/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5Accept-Charsetutf-8, iso-8859-1, utf-16, *;q=0.7Accept-EncodinggzipAccept-Languageen-USHostwww.xhaus.comUser-AgentMozilla/5.0 (Linux; U; Android 2.3.6; en-us; SAMSUNG-SGH-I777 Build/GINGERBREAD) AppleWebKit/533.1 (KHTML, like Gecko) Version/4.0 Mobile Safari/533.1ViaHTTP/1.1 alp2nz04msp1ts02.wnsnet.attws.comX-Att-DeviceidSAMSUNG-SGH-I777/I777UCKK6X-Wap-Profile

Your browser software transmitted the following HTTP headers URL: http://xhaus.com/headers Request parameter Value Requested URI /headers Request Method GET Remote IP Address <REDACTED> Remote IP Port 22141 Protocol version HTTP/1.1 HTTP Header* Value Accept text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Encoding gzip, deflate Accept-Language en-US,en;q=0.5 Connection keep-alive Host www.xhaus.com User-Agent Mozilla/5.0 (Android 4.4; Mobile; rv:41.0) Gecko/41.0 Firefox/41.0 Via HTTP/1.1 alp2nz04msp1ts02.wnsnet.attws.com

So download the max2015 dotXSI exporter and the new version of Carcass from the Utilities section and lets see what BB-8 can do inside JK2/3.

Can't connect on cellphone native browser. Firefox app works fine

Glad to see you back. What version of 3ds Max are you using? I have fixed the dotXSI 3.0 exporters for 3dsMax-- so you can compile your BB-8 and see him inside Jedi Knight! But I forgot to do the coordinate transformation on the vertex normals... so I need to fix that

Can you post some screenshots showing that is in fact the case?

But can you or someone explain to me why it does that? Does Softimage --> Carcass do the same thing? If so, then we need a fix in Carcass to retain original normals along UV Seams, yes?

Yeah, I'd like to come up with a test case for us to check out. We need a "not-too-complicated" model that we can test both vertex normals and UV seams... between Max & Softimage with Carcass. Maybe you, me and @@DT85 can come up with something. Yeah... that looks like I forgot to do the coordinate transformation on the vertex normals. I'll fix it when I add the other vertex normal export options.

This open source engine uses octrees: http://castle-engine.sourceforge.net/vrml_engine_doc/output/xsl/html/index.html Edit: Only suggesting that the coders might look at this to see if an octree data structure can be added to OpenJK engine-- where we retain BSP data structures as children nodes??? Or some other harmonious arrangement between octree and BSP... of course I don't know what I'm talking about :-/

Again... I think he's really asking for an Octree Spatial Partitioned (OSP) data structure for large outdoor maps. http://www.gamedev.net/topic/335852-octtree-vs-bsp/

I think he may be hinting at another data structure for large outdoor scenes... http://stackoverflow.com/questions/99796/when-to-use-binary-space-partitioning-quadtree-octree

Whatever would show the mesh or UV normals. I agree, (@@Xycaleth) Modview needs proper shader & normal map support & light support

If Carcass doesn't show the same UV splits on your Softimage model then it could be the dotXSI exporter doing something with the UV normals... can you post any screenshots that show your mesh and UV normals?

I'll try and have an update on the head mesh, hair, & lip area next week. Thanks for everyone's patience...