• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Error message in MDLTweaker II

Hi Gianni,

arno said:
Humm, it is very weird, but I can't find the option at the moment. While I know I have seen it before. All I know is that this code is not created when I export objects myself. Once I find where it is, I'll let you know.
Click to expand...

OK, I found it again. Check your makemdl.cfg file. If there is a line like Debug=1 in there, you need to remove that one. I think this option is only in the CFG file, not on the GUI.
 
Arno,

do I understand you correct? The version I have should show Textures?
Where should I put the Textures to? It would be great if you can insert a configuration Toolbar, where you can ask me to set the TexturePath.
This would then also work with the FS2004 Library Objects.
This is what I do with our Tools. I set all Paths (Scenery Path, Texture Path, MDL Path) I also realized a Library Creator by myself. So for this I need this configuration to work with more than 1 developer.

If you think it is worth for more users I would be glad.

Thanks
Christoph
 
Hello Arno,

Sorry for my late response - I have been absent
some days.

I performed the download of Martin Wrights dll files,
but this was not helpful.

I get an error message " Error 70 (Zugriff verweigert i.e no access) in procedure
timer preview_ Timer of User ucPreview" trieing to open the edns_hangar_01 mdl, you already received by Christoph.

Greetings
Rolf
 
Hi Christoph,

Yes, the current version of MDL Tweaker II should be able to show your textures, if the program can find the textures files of course.

This is how MDL Tweaker looks for them. First it checks if they are in the same folder as the MDL file. If this is not the case, it will look one folder up and search through any subfolder of that folder for the texture. If still not found, it will move one level up again. This is done for a few levels (can't remember the actual amount). So if the textures can not be found, the searching process can take a while. This is something I want to improve in future versions.

I made it like this, because I don't want MDL Tweaker to be project specific. So you shouldn't have to enter a texture path for each object you are trying to load. MDL Tweaker should just to able to locate the texture itself.

With the current code it is possible to have the textures together with the MDL files. But you could also have the textures in a texture folder, while the MDL files are in the BGL folder. Or a third option is the structure I use, where I have the MDL files in a source subfolder, while the textures are in the texture folder. All these different approaches should work with the current code.
 
Hi Rolf,

r_schon said:
I get an error message " Error 70 (Zugriff verweigert i.e no access) in procedure timer preview_ Timer of User ucPreview" trieing to open the edns_hangar_01 mdl, you already received by Christoph.
Click to expand...

OK, I will try to figure out what that could be. As I said the file opens correct on my PC here, so I don't think the problem is in the MDL object itself. It might be that loading a texture or so does not work.
 
Thanks Arno,

I will test this out. The idea how you search the texture is fine. After I have the textures even on a different drive it can be the reason why I do not see anything.

Coming back to VB. If you need some help soemday try to contact me. I am having experience in programming vor some yours. But After I saw your Preview of the Objects I think you need no help:)
I do not even now how to do so...
Did you do this by yourselve? Great job
Greetings
CHristoph
 
Hello Arno,

Feels good, to be a member here. Thank you for your efforts to solve
my problem.

May be some observations are helpfull for you:

1.I copied my textures to the some folder where my mdl is
located. No success.

2. I detect a time of more than 30 seconds the error message needs
to appear, when I try to open the mdl file with MDL Tweaker II.
Meanwhile the harddsk is working hard. Seems to be a good idea,
that the texture folder can not be found.

Greetings
Rolf
 
Hello Rolf,

r_schon said:
2. I detect a time of more than 30 seconds the error message needs to appear, when I try to open the mdl file with MDL Tweaker II. Meanwhile the harddsk is working hard. Seems to be a good idea, that the texture folder can not be found.
Click to expand...

That sounds a lot like the textures not being found. As I explained in a previous post, it will try to search through other folders to find them. So if they are found nowhere, this will indeed take some time (that is something I need to improve).

The textures that you placed with the MDL object, do they have a weird format or so? MDL Tweaker should be able to read BMP files and DXT BMP files without trouble. Maybe you can email me the MDL object and the textures of it, so that I can try to reproduce the problem here?
 
Hi Christoph,

chrieger said:
Coming back to VB. If you need some help soemday try to contact me. I am having experience in programming vor some yours. But After I saw your Preview of the Objects I think you need no help:)
I do not even now how to do so...
Did you do this by yourselve? Great job
Click to expand...

Yes, I made the preview myself with OpenGL. Was quite a nice challenge to get it working :).

Now that I have the functionality to read a MDL object and create an internal object of it in memory, it is becoming much easier to do things like that with it.
 
Hello Arno,

We use no weird textures. But we have the same set of textures with
identical name and extensions in different folders. We use normally two
texture sets - one for work in progress in a 512x512 true color bmp format to make changes with a drawing programm and the same texture changed in DXT. bmp format in the definite scenery texture folder. Both with same name and extension.

Textures attached
View attachment 1070
 
Last edited:
OK, thanks. After copy the 02 daytexture to have a night variant as well, it loads very fast here and shows as it should. So unfortunately I can not reproduce the error, let me see if I can find anything else.
 
Hello Arno,

after I made a night texture for all textures I had marked by the night
texture button in the texture definition window of FSDS 3 and attached to my texture folder I had no longer an error message with MDL Tweaker and the preview showed correctly.

So, it is important to create a night texture and put it into the texture
folder if ther is a N suffix with a texture in your FSDS3 texture list !!
( I think for development purposes it would be sufficient to create a "dummy" night texture )

These are the good news - but there is a new problem. Closing MDL Tweaker I get an error message :

"Die Anweisung in " 0x696f9f50 " verweist auf Speicher in "0x0000003d".
Der Vorgang "read" konnte nicht auf dem Speicher durchgeführt werden "


Greetings
Rolf
 
I think Arno is already working on this mistake.
But Arno, I am trying some seasonal Texture changes and found some mistakes.
Can I mail you a pdf-file with the description how to get the mistake and a screenshot withe the window?

Greetings
Christoph
 
Hello Rolf,

r_schon said:
So, it is important to create a night texture and put it into the texture folder if ther is a N suffix with a texture in your FSDS3 texture list !! ( I think for development purposes it would be sufficient to create a "dummy" night texture )
Click to expand...

OK, thanks. That is good to know. I guess the runtime error then happened while searching your HD for the textures (it must have hit a folder it was not allowed to read or so).

So I think there are two things I will have to look at. First the way the textures are searched. This should not crash the program if something goes wrong of course, it should just fail to find the texture and continue. Second I think I can exclude the night textures from being found, as they are not display in the preview anyway.

And yes, I am aware of the error at shutdown, the only problem is that I do not have it on my own PC, so that makes it hard to debug.
 
Hi Christoph,

chrieger said:
But Arno, I am trying some seasonal Texture changes and found some mistakes. Can I mail you a pdf-file with the description how to get the mistake and a screenshot withe the window?
Click to expand...

Sure, please let me know anything weird that you find.
 
Arno,

I could not find a way to mail you instead with the help of your websytem.
So I took a email you hade in your readme.
Please give me a info if you did not reseave a mail.
Thanks
Christoph
 
Got your email, thanks.
 
Hi Arno, I found some time to test your latest version. It works fine now.
All Textures are changed in saesonal textures. Great
Thank You
Christoph
 
You must log in or register to reply here.
Back
Top