Hi,
a very common request is for Qt 3D to support the Autodesk FBX file
format which is a pretty standard format for exchanging 3D meshes, and
animations. Unfortunately the format is undocumented and proprietary but
Autodesk does provide a free (as in beer) SDK that can be used to parse
FBX f
On 30 October 2016 at 09:03, Sean Harmer wrote:
> What can we do in terms of pre-compiled release builds of Qt? Is it
> feasible for us to distribute the runtime lib required by the plugin from
> the fbx SDK? Or do we need to find some other solution such as build the
> plugin for the release pac
On domingo, 30 de outubro de 2016 09:03:59 PDT Sean Harmer wrote:
> I guess this is similar to the database driver plugins.
Right.
We ship the compiled plugins for both MySQL and PostgreSQL, but not their
libraries, so the plugins can't be loaded unless the user installs the
required client lib
Greetings,
We use both QT5 and the Autodesk FBX loader in our application - and we
would strongly prefer Qt to NOT link it in.
There is a need quite often for us to update the Autodesk FBX SDK
asymmetrically to QT, and it would be preferable QT doesn't use it in
order to avoid potential conf
Hi,
On 31/10/2016 00:48, Chris Gilbert wrote:
Greetings,
We use both QT5 and the Autodesk FBX loader in our application - and we
would strongly prefer Qt to NOT link it in.
There is a need quite often for us to update the Autodesk FBX SDK
asymmetrically to QT, and it would be preferable QT doe
On 31/10/16 10:08, "Development on behalf of Sean Harmer"
wrote:
>Hi,
>
>On 31/10/2016 00:48, Chris Gilbert wrote:
>> Greetings,
>>
>> We use both QT5 and the Autodesk FBX loader in our application - and we
>> would strongly prefer Qt to NOT link it in.
>>
>> There is a need quite often for us
Hi Lars,
On 31/10/2016 09:22, Lars Knoll wrote:
On 31/10/16 10:08, "Development on behalf of Sean Harmer"
wrote:
Hi,
On 31/10/2016 00:48, Chris Gilbert wrote:
Greetings,
We use both QT5 and the Autodesk FBX loader in our application - and we
would strongly prefer Qt to NOT link it in.
On Mon, Oct 31, 2016 at 01:06:04PM +, Sean Harmer wrote:
> On 31/10/2016 09:22, Lars Knoll wrote:
> > It might make sense to rethink this, and provide those plugins as
> > standalone source packages, that can be easily compiled within
> > creator by our users. That would of probably also requir
On segunda-feira, 31 de outubro de 2016 13:06:04 PDT Sean Harmer wrote:
> > It might make sense to rethink this, and provide those plugins as
> > standalone source packages, that can be easily compiled within creator by
> > our users. That would of probably also require that they live in a
> > repo
> Is it really too difficult to download the qt3d source tarball, cd
somewhere,
> type qmake && make?
It does make this kind of functionality hard to test for people outside of
the hardened Qt community. Well documented manual processes are always an
acceptable baseline, but they introduce a barri
On lunes, 31 de octubre de 2016 9:22:34 A. M. ART Lars Knoll wrote:
[snip]
> We’re facing the same problem in a couple of places in Qt. For
> postgres/mysql we provide a precompiles plugin, but don’t ship the client
> libs which has proven to be problematic, as users wonder why it doesn’t
> work, o
Sean Harmer wrote:
> Yeah, trouble with that approach is we are always chasing feature
> support and we'd rather focus efforts elsewhere.
And just running Blender's Python FBX converter
(https://wiki.blender.org/index.php/Extensions:2.6/Py/Scripts/Import-Export/Autodesk_FBX)
as is and then working
Hi,
On 05/11/2016 02:34, Kevin Kofler wrote:
Sean Harmer wrote:
Yeah, trouble with that approach is we are always chasing feature
support and we'd rather focus efforts elsewhere.
And just running Blender's Python FBX converter
(https://wiki.blender.org/index.php/Extensions:2.6/Py/Scripts/Impo
13 matches
Mail list logo
