L3DT_Atlas

[MDynna]

Hi Aaron,

I'm trying to use the latest version of the L3DT_Atlas plugin. Whenever I try to export a map with a size > 2048 I get a warning message. However, whether I click Yes or No on the warning I get the same errors in my log:

Code: Select all

L3DT Atlas Export - user cancelled export after >2048 HF warning.

CZeoFunc::CallFunction error:
 - The function 'ExtSaveAtlasFile' in the plugin 'l3dt_atlas' returned an error.

zeofunc_file_export_atlasHelper error:
 - call to export function failed

CZeoFunc::CallFunction error:
 - The function 'atlasEx' in the plugin 'L3DT-CORE' returned an error.


Notice the first line: user cancelled export... I get this regardless of pressing Yes or No on the warning. I know you don't have anything to do with the plugin itself, but this warning message seems to originate inside L3DT (I couldn't find it in the plugin source). Could you please confirm that the problem isn't something simple like that warning always returning "No"?

[Aaron]

Hi Mark,

Oh, I had never seen that message before, which means it's not one of mine. Indeed, the second message identifies the culprit:

"The function 'ExtSaveAtlasFile' in the plugin 'l3dt_atlas' returned an error."

What this means is that the message is shown either in the 'ExtSaveAtlasFile' function in the plugin or a subroutine thereof, and the whole export is failing because that plugin function subsequently returns false. The error messages that then follow are are the result of the error cascading out from that function through another wrapper plugin function ('atlasEx' in 'L3DT-CORE'). The 'CZeoFunc' bit is just a wrapper used to call the plugin functions, which automatically logs an error whenever a plugin function returns false.

Cheers,
Aaron.

[MDynna]

Ok, I'll dig into the plugin's code to try to find the source. Thanks Aaron.

[dr_boom]

I get the same thing.

[MDynna]

Well, I just got the darned thing to compile yesterday, so now I have a chance to try and find out what's wrong.

Of course, when you let GG know about it their response is: "You've got the source code..."

[dr_boom]

MDynna, did you do anything different to get it to compile?

[MDynna]

Yes, I had to do a lot of different things actually. Check out the instructions I posted in this thread on the GG forums.

[dr_boom]

Thanks, but I cannot access that forum unfortunately. Can you copy and paste it here maybe?

Thanks again

[MDynna]

Sorry, I can't. If you own a license to TGEA then you should be able to access that forum and you can contact GG in that case to resolve the problem.

If you don't own a license to TGEA, then you shouldn't have the source code for l3dt_atlas in the first place.

[dr_boom]

I misred that post but see it now, i did not realize you were messing with the source code...thought you were messing with some of the plugin variables within l3dt to get it to go. I just map for a project using the engine.

[MDynna]

Oh, yeah. This is certainly a source change. Though if you own L3DT Pro (which it appears you do) then I can release a compiled version of my changes once I'm done.

[dr_boom]

Yes i do. That's very generous of you to release it as well and much appreciated.

Thanks!

[MDynna]

Ok, TGEA 1.02 has been released and I finally got my hands on the latest source code for this plugin, and after approximately 30 seconds of work I fixed the plugin.

What's that you say? Why could I fix it so quickly? Well, that's very simple. It's because the error I have been getting all along was exactly what I thought it was. Namely, after that "bigger than 2048" dialog box is shown the plugin doesn't properly check the DIALOG BOX RESULTS! Thus, it always thinks the answer is "No." I mean, for freak's sake, it's not like it was hard to replicate.

Aaron is there somewhere I can upload the new binary for everyone who owns L3DT Pro?

[Aaron]

Hi Mark,

Well done. If you send the file to me directly (aaron@bundysoft.com), I'll put it up on the pro downloads page - at least until GG updates the 'official' build, which I hope will be shortly.

Best regards,
Aaron.

[Aaron]

Thanks Mark,

Your updated plugin is now available for download on the Pro downloads page.

Best regards,
Aaron.