[Soc-2012-dev] no import and no error log with fbx import

[Alexander Gessler]

Hi again,

I fixed the first issue - negative material indices are now resolved to
the default material.

What I get is this:

http://www.greentoken.de/privat/fbx2.png

Does that look right? I'm asking because I can't get Autodesk FBX
Converter to show something meaningful for this scene.

The geometry is a bit strange, but not so strange that I would be sure
that it was not intended as such.

Would be great if you could spare the time for another try! (you will
need to svn update on bratwurst and rebuild)

Bye, Alex

On 8/10/2012 4:19 PM, Alexander Gessler wrote:
> Hi Benny,
> 
> thanks for posting the file.
> 
> I can confirm its an issue with the importer.
> 
> The file specifies negative material indices (which I didn't see
> before in any fbx file I've encountered so far).
> 
> The message assimp dies with is:
> 
> "FBX-DOM: encountered negative integer index" (+ line, column number)
> 
> Running on Windows, I do actually see that error message show up in
> Blender, too - strange. Are you sure it doesn't show up? Maybe you can
> grep for the exact text?
> 
> Will fix the issue.
> 
>> And still no debug output. Can you imagine how frustrating this
>> is?
> 
> Sure - but this is WIP, not a feature for productive use yet :-/ You
> will need to give it some months to become mature.
> 
> Bye, Alex
> 
> 
> On 8/10/2012 3:35 PM, Benjamin Dahl - post at bennyd.de wrote:
>> Hi Alex,
>>
>> yes I'm quite sure I build with fbx and assimp support since it
>> shows up in the menu (see screenshot) 
>> https://dl.dropbox.com/u/1944337/Betatest/Bildschirmfoto%202012-08-10%20um%2015.03.12.png
>>
>>  and I doublechecked it before building. This is the part from my
>> scons user-config.py
>>
>> # note: WITH_BF_FBX==True needs WITH_BF_ASSIMP to be enabled as
>> well WITH_BF_ASSIMP = True WITH_BF_FBX = True
>>
>>
>> … and I also checked, if it works with fbx files previously
>> converted to 2013 ascii format. It doesn't. 
>> https://dl.dropbox.com/u/1944337/Betatest/Bildschirmfoto%202012-08-10%20um%2015.18.16.png
>>
>>  And still no debug output. Can you imagine how frustrating this
>> is?
>>
>> Can you check, if this is an issue with my file? 
>> https://dl.dropbox.com/u/1944337/Betatest/Raum_1_Final_benny1_2013ascii.fbx
>>
>>  The fbx-file is rather simple and for testing purpose only so far.
>> In the Future I have to work together with someone who is using
>> cinema4d for architecture visualizations and we have bad
>> experiences with the collada exchange between cinema4d and
>> blender. So we're hoping the fbx-bridge will do it better then.
>>
>> bye Benny
>>
>>
>> Am 10.08.12 12:52 schrieb Alexander Gessler:
>>> Hi Benny,
>>>
>>> you need to convert all your fbx files to 2013 _text_ (ascii)
>>> format first (using FBX Converter!).
>>>
>>> Are you sure you have built with WITH_ASSIMP and WITH_FBX?
>>>
>>> Normally you should get a whole bunch of logging errors because
>>> I'm basically piping assimp's entire logging into Blender.
>>>
>>> Hope that helps.
>>>
>>> Bye, Alex
>>>
>>> On 8/10/2012 12:52 PM, Benjamin Dahl - post at bennyd.de wrote:
>>>> Hello,
>>>>
>>>> After getting the blender bratwurst build with fbx import to
>>>> run on my ubuntu machine yesterday, I was so happy because I
>>>> thought, I can start to test the importer now. Apperently this
>>>> has been a delusion. Trying to import either my own fbx files
>>>> or the samples from the autodesk fbx-converter didn't work at
>>>> all. Nothing was imported and as a result I had this error in
>>>> the »info window« in blender:
>>>>
>>>> »Errors found during importing. Please see console for error
>>>> log.«
>>>>
>>>>
>>>> Since I launched blender from command line, I thought errors
>>>> must be found there. But they aren't.
>>>>
>>>> So I compiled the whole thing again now with the BF_Debug
>>>> option enabled, but no error log appears when trying to import
>>>> fbx-files.
>>>>
>>>> Then I started blender again with gdb ./blender but even there
>>>> are no more error messages.
>>>>
>>>> Last thing I tried, was starting blender from command line with
>>>>  --debug-all option but I got so many messages that I tried to 
>>>> filter that with grep or wrote them into a error.log file like 
>>>> this
>>>>
>>>> ./blender --debug-all | grep fbx ./blender --debug-all >
>>>> error.log
>>>>
>>>>
>>>> No Output there.
>>>>
>>>>
>>>> It's completely frustrating, that I managed to compile the
>>>> whole stuff and testing fails at the early beginning now,
>>>> because nothing is imported
>>>>
>>>> Every help is appreciated. There's nothing more I'd love to
>>>> have than a blender binary build with fbx-import enabled.
>>>>
>>>> cheers
>>>>
>>>> Benny
>>>>
>>>> -- Dipl.-Des. Benjamin Dahl Finowstraße 9 10247 Berlin Germany
>>>>
>>>> Phone: +49 (30) 83217244 (Berlin) Mobile: +49 (176) 21300553
>>>>
>>>> Email: post at bennyd.de Web: http://www.bennyd.de/
>>>>
>>>>
>>>>
>>>> _______________________________________________ Soc-2012-dev 
>>>> mailing list Soc-2012-dev at blender.org 
>>>> http://lists.blender.org/mailman/listinfo/soc-2012-dev
>>>>
>>
>>
>>
>>
>>
>> _______________________________________________ Soc-2012-dev
>> mailing list Soc-2012-dev at blender.org 
>> http://lists.blender.org/mailman/listinfo/soc-2012-dev
>>
> 
> _______________________________________________
> Soc-2012-dev mailing list
> Soc-2012-dev at blender.org
> http://lists.blender.org/mailman/listinfo/soc-2012-dev
>