I don't know why, but the FBX2EDF converter has suddenly decided to literally crash 3 quarters of the way through it's usual time frame for completing a .map with shadow sampling run. This is such a soul destroyer as it takes at least an hour before I know whether it's going to work or not right now. :(
Just installed all the latest Win 7 X64 updates today. Also tried a total fresh reboot of my system.
This is strange because it was working fine before now.
I have tried 4 consecutive runs and all 4 runs crashed at about the same time 1.2 hrs into the session.
Screenshot of what happens when it crashes below:
(https://c2.staticflickr.com/6/5819/30883960865_931447ae5c_o.jpg) (https://flic.kr/p/P47nzT)
Hawk.
Just tried using the latest released FBX2EDF Converter again to export the Silverstone v0.96 model. The problem seems to happen when converting the full terrain part of the model when using the "Shadow Map" and "Shadow Volumes" options on the FBX2EDF Converter(as illustrated in the pic above).
The track converts okay with the shadow options selected if I leave out the full terrain model and just convert the track with immediate side terrain sections and peripheral buildings and models, but crashes after 1hr 10 mins if I include the full terrain model.
Is this a bug?
Hawk.
@Piboso: I've been using the FBX2EDF Converter to process an FBX track file, and it's been running now for nearly 3hrs without completion. :o
Would you suggest that the FBX2EDF Converter is still working Piboso? Or has it likely crashed without letting me know? I'm at pains to stop it after waiting so long but after 3hrs of it supposedly processing the track file I'm seriously doubting that it's still working on the file at all?
Suggestion for a future user experience improvement: It would be good to have some sort of animated working graphic so that the user can know whether the application is actually doing it's job or stopped working altogether? :)
Hawk.
Quote from: Hawk on January 24, 2017, 02:49:04 PM
@Piboso: I've been using the FBX2EDF Converter to process an FBX track file, and it's been running now for nearly 3hrs without completion. :o
Would you suggest that the FBX2EDF Converter is still working Piboso? Or has it likely crashed without letting me know? I'm at pains to stop it after waiting so long but after 3hrs of it supposedly processing the track file I'm seriously doubting that it's still working on the file at all?
Suggestion for a future user experience improvement: It would be good to have some sort of animated working graphic so that the user can know whether the application is actually doing it's job or stopped working altogether? :)
Hawk.
UPDATE: This conversion has just finished...... MY GOD! 3hrs 34mins to convert this track. WFT?! :o :o >:(
Don't get me wrong, I realise that track files can take a long time to process, but I've never had a track file in the past take more than 2hrs at most, and I've processed a lot of track files for GPB in my time.
Just what on earth would cause a track file, that is nowhere near as complex as some I've processed in the past, take SO long to process?? To say I'm not pleased is a HUGE understatement! >:(
Sorry for the outburst, but this on top of the things this FBX2EDF Converter doesn't do that it should do is getting very, very frustrating to say the least. ::)
Hawk.
@Piboso: Just a quick yes or no answer please will do: Does the FBX2EDF converter support the use of .dds texture files in the FBX track scene for conversion?
Hawk.
Quote from: Hawk on February 18, 2017, 12:57:35 PM
@Piboso: Just a quick yes or no answer please will do: Does the FBX2EDF converter support the use of .dds texture files in the FBX track scene for conversion?
Hawk.
DDS textures should be supported.
Quote from: Hawk on February 18, 2017, 12:57:35 PM
@Piboso: Just a quick yes or no answer please will do: Does the FBX2EDF converter support the use of .dds texture files in the FBX track scene for conversion?
Hawk.
I can vouch for DDS being supported. I used them for all the trees on the JS7 compound for MXB. They seemed to suffer much less from the alpha glowing edges problem. Also doubling up the tree model solves this for the most part albeit in an uneconomic way.
As soon as I start the FBX2EDF converter on an .fbx track scene with all .dds textures, it's saying that a texture called "WindowRef.dds" is invalid or non-existent and the converter then crashes every time. But the texture is definitely existent and I cannot understand why it would be invalid?
I've never had that problem before when dealing with .bmp or tga textures, this is why I'm wondering if it's a .dds issue?
I'll try the 3dsmax edf-exporter and see if that crashes too.
Hawk.
Check the format, there are a few different versions of DDS.. Gimp allows you to export with many options too.
The Track Creation Rules Wiki details the versions of DDS supported.
The only time i get that message is when the material to texture link path is incorrect.
So the texture is present, and the UV is mapped to it but the texture linked to the material has a corrupt path
Thanks for the advice and info guys... I'll check it out. Appreciated. ;) 8)
Hawk.