Page 4 of 4

PostPosted: Mon May 07, 2007 11:44 am
by Aaron
Hi Carl,

I've just uploaded a new dev build with custom map layer support (L3DT Pro 2.5.0.32, 7th of May). To create a custom map layer, use the 'Utilities->New map layer' menu option. To edit the map layer, click on the 'Edit' toolbar button. Currently, the editing tools are quite basic, but they might be enough for the purpose of building your Spring feature maps. Please let me know what you think.

Best regards,
Aaron.

Re: All done!

PostPosted: Mon Jun 04, 2007 9:41 am
by Q-dad
carldt wrote:Here's the steps:

1) Get Python here:

http://www.python.org/ftp/python/2.5/python-2.5.msi

2) Then get cdPython here:

http://l3dtpython.googlecode.com/files/cdPython-0.5.zip

3) Go to D:\Install\Bundysoft\L3DT Standard 2.5 RC3 (or wherever L3DT.exe is installed) extract the cdPython.zip to here.

4) Get a script to try out, like HFtoBMP:

http://l3dtpython.googlecode.com/files/HFtoBMP.py

5) Create a Terrain.

6) Start L3DT, go to cdPython->Run a Python script, browse to HFtoBMP.py, press OK, enter a filename in the text box (without the BMP extension), press OK

7) Go to the folder where the HFtoBMP.py script is and there should be a BMP file with the filename you gave.

Well, I've tried this, but it stops at 6) --> I can't find cdPython inside L3DT. I guess it should have been among the extensions, but it's not. If I try to load it through the extension manager, I get this error message...:

CExtDLL::LoadDLL error:
- call to LoadLibrary failed for 'D:\Programfiler\L3DT Professional 2.5.1.2\Extensions\cdPython.dll'
- Plugin requires additional dependencies that were not found.

CExtManager::LoadDLL error:
- Call to CExtDLL::LoadDLL failed

What am I doing wrong...?

PostPosted: Mon Jun 04, 2007 12:58 pm
by carldt
Version 0.10 is the latest. Can you try this?

http://l3dtpython.googlecode.com/files/cdPython-0.10.zip

I will try it with a new version of L3DT shortly.

PostPosted: Mon Jun 04, 2007 1:17 pm
by Aaron
Is this another case of the missing msvcr80.dll?

PostPosted: Mon Jun 04, 2007 1:57 pm
by Q-dad
Ok, forgot to say that I was using v0.10, and not v0.5 as quoted...

PostPosted: Tue Jun 05, 2007 12:22 am
by carldt
aaron wrote:Is this another case of the missing msvcr80.dll?


Unlikely, I went to a lot of trouble with the last version to compile it using 2003 compiler tools, so it should be linked agains msvcr70.dll

PostPosted: Tue Jun 05, 2007 12:45 am
by Aaron
Hmmm...maybe missing msvcr70.dll then? L3DT doesn't install the runtimes because it statically links to MFC. Otherwise, it may be that cdPython can't find python25.dll. Maybe it's not in system32?

PostPosted: Tue Jun 05, 2007 6:14 am
by Q-dad
Well, maybe it's just me doing something wrong, or does any of you also have the same problem...?

PostPosted: Wed Jun 06, 2007 10:26 am
by carldt
Hi,

I have just downloaded L3DT 2.5a and cdPython-0.10 and it works fine.

Looking at cdPython.dll using depends, I can see the following dependencies:

Python25.dll
Kernel32.dll
User32.dll
Comdlg32.dll
Shell32.dll
Msvcr71.dll

The likely candidates that you are missing are Python25.dll and Msvcr71.dll. Since you say you have installed Python25 using the Python installer, that leaves Msvcr71.dll.

Normally, developers redistribute this dll with their application. L3DT is as Aaron says statically linked, so he doesn't need to redistribute it.

Could you please search your computer for msvcr71.dll, and then copy it into either the folder where L3DT.exe is, or, the \windows\system32 folder?

If you cannot find this file, then I guess I can include it in the cdPython zip file.

Thanks,
Carl

PostPosted: Wed Jun 06, 2007 12:16 pm
by Q-dad
Hi,

It was all my fault, it seems... I failed to realize that I had to install python first... :oops:

After installing python, I copied the python25.dll file to the System32 folder, and now it works as intended... 8)

PostPosted: Mon Oct 13, 2008 12:33 am
by carldt
Hi,

I have pretty much stopped maintaining this plugin...

If anyone is interested in taking over the python plugin, let me know.

Thanks.