Thanks for the info. I’m still finding it pretty usable, but i wasn’t aware of its shortcomings. Makes sense that you wont be updating the plugin now!

Somewhere on the road map is to have -every- art asset have some kind of reasonably WYSIWYG (within the limits of 2-d orthographic projection) preview!

I hope and WYSIWYG for painted lines (.lin) too!

Maybe I’ve missed something in a new release but:
– AC3D doesn’t actually support animation. My plugin tries to hack animation into place via plugin trickery. It’s barely usable. For example, you can’t edit your model unless it’s in its rest pose because the editor itself doesn’t know the crazy animation things the plugin has done.
– Therefore there’s really no hope of doing skeletal animation, which is how the next-gen OBJ format is going to work. Every real 3-d modeler can do this.
– AC3D doesn’t let you move a mesh without editing its vertices (or animate this way).
– As you said, it doesn’t bake.
– The number and power of modeling features, such as slicing, topology operations, UV unwrapping…it’s not in the same class as serious 3-d modeling programs.

Ah – my mistake – I totally mis-read this.

Yes, a TMS server is a possibility. But…where will the tiles come from? File a feature request with a -specific- tile server that we can use within our license that is useful to X-Plane users and I will take a look. (In the past, the only requests I have gotten have been Google and Bing – both license-incompatible.)

I’m not that excited about WMS…I think the world has basically figured out that serving pre-cut tiles is a much better architecture than having the server do a bunch of poorly scaling server-side image processing every time the client scrolls. 🙂

Re: JOSM, at this point so many of the high priority feature requests in WED are very X-Plane specific:
– WYSIWYG Taxi sign editing
– WYSIWYG facade editing and facade textured previews
– Output to MeshTool
– Writing DSF road networks

It does? Please enlighten me!

It’s done everything i’ve required it to so far, except baking Ambient Occlusion.

You read it too quickly I am afraid, I said the exact contrary, in particular I do not blame any WED bug but just point the lack of one (important to my mind) feature.

I repeat :
(1) WED does not have an automatic TMS viewer capability
(2) therefore many users end-up stretching their orthophotos “by hand” when building their apt.dat file (of course I know it is not the right way to do it but this
is just a fact) and THAT leads to wrongly placed runways.
(3) I mentioned that perhaps you didn’t include such a viewer because that would imply some additional reprojections (which few viewers are able to) but said that EVEN not doing a reprojection wouldn’t be noticable on the scale of an airport (and you ask me to prove the contrary to what I said).

On the second point: my viewpoint is that WED and JOSM are both tools to encode vector data (one in OSM format, the other in DSF, this a essentially a matter of translation). Since the latter is largely developped and also very good, I suggested the possibility to build upon it rather than building things from scratch (but I admit it is probably too late now).

Hi Oscar,

Please file a bug against WED for Mercator projection. If you have a good real-world example where (1) the error of not having a real projection causes an error and (2) the use case is realistic, please attach it so I can see what’s going on.

Regarding JOSM, I’m not sure what problem you’d be trying to solve – WED and JOSM sort of work in different problem domains.

I do not plan to update the AC3D plugin. AC3D lacks native support for the things we need in a 3-modeler for X-Plane.