-
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.
base file not accessible error
- Thread starter paul64
- Start date
Don't know what to tell you, Paul. If the models are where they should be and are valid, AFLT will find and use them. I have just created a library including every FSX stock model without difficulty using the latest version of AFLT (2.0.02).
Are you using Version 2.0.02? If not, try updating to it.
If you zip up your entire AFLT Library Folder and send it to me, I'll see if anything "jumps out at me".
Don
Are you using Version 2.0.02? If not, try updating to it.
If you zip up your entire AFLT Library Folder and send it to me, I'll see if anything "jumps out at me".
Don
So use the "split" light instead. Only one attachpoint. AFLT uses separation planes to display the correct color.
. Once you've generated the library, there's nothing more to compile.
I can't do anything with a single .mdl file. I need your whole Library Folder. Since it seems to be the mdl. file that's the problem, i may also be helpful if you included the Gmax file for the model.
Don
- Messages
- 8
- Country
Hi,
I join this thread because I have the "base file not accessible error" problem, too, even with AFTL Version 2.0.02 (running with administrator privileges).
I read the user manual, but many basics are still unclear:
1.) After download and unzip "Downloads_AFLT2002" where should I copy it to? Would "Desktop/Private/AFLT/Test1" work? This is my try so far.
2.) The result of "Create/Save Element" is attached below (inside the whole "Test1"-folder)
3.) Klick on "Make Library" -> "Make Object Library"-Panel: the lists for FS9 Models and FSX Models are nearly empty. There's only a checkbox with the name of the previously generated Element ("ElementTest1")
4.) "Library Save Folders": do I have to choose a folder inside the FSX-installation or could it be here: "Desktop/Private/AFLT/Test1/scenery" ?
5.) whatever I do, the result is always: File "Test1" base file not accessible. Continue?
6.) AFLT can't find the models, correct? Where should it be, how could I tell AFLT where they are?
Thanx for help.
Wolfgang
I join this thread because I have the "base file not accessible error" problem, too, even with AFTL Version 2.0.02 (running with administrator privileges).
I read the user manual, but many basics are still unclear:
1.) After download and unzip "Downloads_AFLT2002" where should I copy it to? Would "Desktop/Private/AFLT/Test1" work? This is my try so far.
2.) The result of "Create/Save Element" is attached below (inside the whole "Test1"-folder)
3.) Klick on "Make Library" -> "Make Object Library"-Panel: the lists for FS9 Models and FSX Models are nearly empty. There's only a checkbox with the name of the previously generated Element ("ElementTest1")
4.) "Library Save Folders": do I have to choose a folder inside the FSX-installation or could it be here: "Desktop/Private/AFLT/Test1/scenery" ?
5.) whatever I do, the result is always: File "Test1" base file not accessible. Continue?
6.) AFLT can't find the models, correct? Where should it be, how could I tell AFLT where they are?
Thanx for help.
Wolfgang
Wolfgang, The message mean the library generator is unable to find the specified .mdl file. And that's not surprising, since there are no files in the Bases folder you sent me - which is where AFLT expects to find all models.
You may install AFLT anywhere you like. But, since you seem to have installed it on the C: drive, I expect you will have to "Run as administrator" to make anything happen. To Windows, running with administrator privileges is not the same a running as administrator.
Normally, I would have expected an error message to have been generated when you attempted to save the model if the save was not successful. But, upon examining the code, I find that error message may have been suppressed. Please try again running as administrator and let me know how you make out.
Don
You may install AFLT anywhere you like. But, since you seem to have installed it on the C: drive, I expect you will have to "Run as administrator" to make anything happen. To Windows, running with administrator privileges is not the same a running as administrator.
Normally, I would have expected an error message to have been generated when you attempted to save the model if the save was not successful. But, upon examining the code, I find that error message may have been suppressed. Please try again running as administrator and let me know how you make out.
Don
- Messages
- 8
- Country
Hi and thanx for your reply.
I tried the same thing on another computer, where FSX and FSX-SDK are installed not on C: but on F: (so there should be no more problems about admin-rights...). But unfortunately I had no luck.
AFLT is copied in a subfolder of D:
The content of the AFLT folder - see screenshot 01
After starting AFLT.exe as administrator (as I did before) the main panel opended. I entered more or less the same parameters as before - see screeshot 02
On screenshot 03 you can see the content of the automatically created folder "Test01".
Screenshot 04: After klick on "Create/Save Element" (no warnings or error messages appeared)
Screenshot 05: After klick on "Make Library" and screenshot 06 with entered parameters
Screenshot 07: the final dissapointing error message
Again I attached the zipped "Test01"-folder and the zipped folder of "Downloads_AFLT2002". Maybe there's something wrong...
I'm working with many other scenery developing tools for a long time, but AFLT is the first one I'm struggling with such a strange problem...
Thanx for your help.
Wolfgang
I tried the same thing on another computer, where FSX and FSX-SDK are installed not on C: but on F: (so there should be no more problems about admin-rights...). But unfortunately I had no luck.
AFLT is copied in a subfolder of D:
The content of the AFLT folder - see screenshot 01
After starting AFLT.exe as administrator (as I did before) the main panel opended. I entered more or less the same parameters as before - see screeshot 02
On screenshot 03 you can see the content of the automatically created folder "Test01".
Screenshot 04: After klick on "Create/Save Element" (no warnings or error messages appeared)
Screenshot 05: After klick on "Make Library" and screenshot 06 with entered parameters
Screenshot 07: the final dissapointing error message
Again I attached the zipped "Test01"-folder and the zipped folder of "Downloads_AFLT2002". Maybe there's something wrong...
I'm working with many other scenery developing tools for a long time, but AFLT is the first one I'm struggling with such a strange problem...
Thanx for your help.
Wolfgang
Attachments
Wolfgang, from you screenshots, I can see that the .mdl file has been created and is in the right place. And, it would seem AFLT's inability to find it has nothing to do with access privileges.
I note you are using the latest development release. Since you are using FSX, the latest general release would seem to do everything you need. (2.0.02 provides additional functionality primarily for use with P3D.) So, I would suggest you revert to the latest general release (simply download it and install it over 2.0.02). Be sure to copy the included effects into your effects folder. There's no need to retain the Effects folder otherwise.
I'll investigate this issue in the near future. Unfortunately, 2.0.02 does not provide completely satisfactory operation with P3Dv2 due to the differences in effects operation between P3D and FSX. Now that LM has introduced P3Dv3, I need to update 2.0.02 and retest the effects operation with v3. If LM has not addressed the effects issues troubling AFLT, I expect I will abandon 2.0.02 and AFLT will not likely ever become P3D-compatible.
Sorry, I can't offer you a fix at this time.
Don
I note you are using the latest development release. Since you are using FSX, the latest general release would seem to do everything you need. (2.0.02 provides additional functionality primarily for use with P3D.) So, I would suggest you revert to the latest general release (simply download it and install it over 2.0.02). Be sure to copy the included effects into your effects folder. There's no need to retain the Effects folder otherwise.
I'll investigate this issue in the near future. Unfortunately, 2.0.02 does not provide completely satisfactory operation with P3Dv2 due to the differences in effects operation between P3D and FSX. Now that LM has introduced P3Dv3, I need to update 2.0.02 and retest the effects operation with v3. If LM has not addressed the effects issues troubling AFLT, I expect I will abandon 2.0.02 and AFLT will not likely ever become P3D-compatible.
Sorry, I can't offer you a fix at this time.
Don
- Messages
- 8
- Country
Hi,
I'm still very confused.
Testing Version 1.1.0.3. get's the same error message in the end.
You said, the .mdl file has been created and is in the right place. Ok.
But AFLT can't find it - why? Or is it looking for another file? Or should the .mdl file be stored somewhere else?
Why don't other users have this problem...?
What can I do with the .mdl file? I thought, AFTL would create a .bgl file (with "Make Library") to place it my scenery (with Instant Scenery or other tools). But I can't find a .bgl file...
You said, I should install Version 1.1.0.3. "Install" means, just unzip the downloaded folder somewhere and doubleklick AFLT.exe - correct?
I hope you can help me
Maybe you could create a basic object like a PAPI and post your screenshots here (including your "Test01" folder). So I could compare them to mine... (and to your "Test01" folder).
Thanx.
Wolfgang
I'm still very confused.
Testing Version 1.1.0.3. get's the same error message in the end.
You said, the .mdl file has been created and is in the right place. Ok.
But AFLT can't find it - why? Or is it looking for another file? Or should the .mdl file be stored somewhere else?
Why don't other users have this problem...?
What can I do with the .mdl file? I thought, AFTL would create a .bgl file (with "Make Library") to place it my scenery (with Instant Scenery or other tools). But I can't find a .bgl file...
You said, I should install Version 1.1.0.3. "Install" means, just unzip the downloaded folder somewhere and doubleklick AFLT.exe - correct?
I hope you can help me
Maybe you could create a basic object like a PAPI and post your screenshots here (including your "Test01" folder). So I could compare them to mine... (and to your "Test01" folder).
Thanx.
Wolfgang
When I made that statement previously, I thought that only valid .mdl files would be listed by the Make Library function. However, upon checking the code, it seems only the .ini file is necessary. Upon rechecking your screenshots, it's clear that no .mdl files have been created - which changes the whole nature of the issue.
Good question. But, as you can see, no one else is reporting the problem - nor have I ever experienced it. That's the reason I suggested you revert to 1.1.03. But you are reporting the same thing occurs with the general release. Since the C: drive is not involved, that only leaves one thing - the data you are entering. AFLT should identify such an error but that would seem not to be the case.
The only thing I notice in your data is that you have not specified the hours of operation. Without doing a detailed analysis of the code (for which I don't have time at the moment) I suspect AFLT is "tripping" over that and not creating the .mdl file. Try checking the 24 hr. checkbox.
If that's not the issue, you'll have to leave it with me.
Don
Wolfgang, I had a minute to spare so I thought I'd test my theory about operating hours not being specified. That's not the problem.
What I have discovered is an oversight in 1.1.0.3 compounded by a coding error in 2.0.02. However, the problem only affects creation of custom models - and few users actually do that - the likely reason for it not having been reported previously. I will get it fixed ASAP. In the meantime, you will be unable to create custom models.
Don
What I have discovered is an oversight in 1.1.0.3 compounded by a coding error in 2.0.02. However, the problem only affects creation of custom models - and few users actually do that - the likely reason for it not having been reported previously. I will get it fixed ASAP. In the meantime, you will be unable to create custom models.
Don
Please try Development Release 2.0.03, now available at http://stuff4fs.com and confirm the problem is resolved.
If it fixes your problem, I will apply a similar fix to the general release.
Don
If it fixes your problem, I will apply a similar fix to the general release.
Don
- Messages
- 8
- Country
Hi and thanx for your help
Version 2.0.0.3 is in fact creating a bgl. file !
I attached the resulting folder "Test10".
But: when I import the bgl. file into ModelConverterX it looks a little bit strange (see mcx_01.jpg and the report created by MCX: mcx-report.zip)
The 4 PAPI units, which should later be visible in the scenery are far below the ground and the 4 effect objects are far behind the center... If I insert this bgl. file in a scenery it isn't visible unless I change the elevation of this object...
Is this what AFLT should create or was something going wrong?
Next: if I made the PAPI-object visible in a scenery (I have to change the elevation of this object from 0 to 100.70) it shows always white lights, no change to red in any position of the aircraft; and the lights are even visible from behind the PAPI units...
Maybe you can help me again
Thanx
Wolfgang
Version 2.0.0.3 is in fact creating a bgl. file !
I attached the resulting folder "Test10".
But: when I import the bgl. file into ModelConverterX it looks a little bit strange (see mcx_01.jpg and the report created by MCX: mcx-report.zip)
The 4 PAPI units, which should later be visible in the scenery are far below the ground and the 4 effect objects are far behind the center... If I insert this bgl. file in a scenery it isn't visible unless I change the elevation of this object...
Is this what AFLT should create or was something going wrong?
Next: if I made the PAPI-object visible in a scenery (I have to change the elevation of this object from 0 to 100.70) it shows always white lights, no change to red in any position of the aircraft; and the lights are even visible from behind the PAPI units...
Maybe you can help me again
Thanx
Wolfgang
Attachments
Last edited:
Glad to hear the initial problem is now fixed. I'll make a new general release soon.
As for the MCX display, I doubt MCX can display what you want to see. AFLT objects are animated. Effects cannot be easily turned on and turned off. In AFLT, lights are always on. When they are supposed to be off, they are placed 100ft below ground so they cannot be seen. That's probably what you are seeing below ground
You haven't said what version of Flightsim you are using. If P3D, note I said above AFLT effects-based objects don't play well in P3Dv2.
I have examined the library .bgl file you sent. (Unfortunately, the .mdl file does not appear in the files you sent.) It appears normal. However, I am unable to display you PAPI - even 101; above ground.
Assuming you are using the same Main Panel parameters as in your earlier report, I will attempt to duplicate the problem "from scratch". I'll get back to you.
Don
As for the MCX display, I doubt MCX can display what you want to see. AFLT objects are animated. Effects cannot be easily turned on and turned off. In AFLT, lights are always on. When they are supposed to be off, they are placed 100ft below ground so they cannot be seen. That's probably what you are seeing below ground
You haven't said what version of Flightsim you are using. If P3D, note I said above AFLT effects-based objects don't play well in P3Dv2.
I have examined the library .bgl file you sent. (Unfortunately, the .mdl file does not appear in the files you sent.) It appears normal. However, I am unable to display you PAPI - even 101; above ground.
Assuming you are using the same Main Panel parameters as in your earlier report, I will attempt to duplicate the problem "from scratch". I'll get back to you.
Don
- Messages
- 8
- Country
Hi,
I using FSX.
Attached are the mdl. file (papi4test10.mdl from Lights folder), the screenshots from my entries in the AFTL panels and screenshots from FSX+Instant Scenery-Tests (the same object from different angles).
In MCX I can start and watch the animated light effects: they are wandering from the back to the center...
Could you make are screenshot of a PAPI in a scenery which is exactly working how it should? So I can see the difference?
I using FSX.
Attached are the mdl. file (papi4test10.mdl from Lights folder), the screenshots from my entries in the AFTL panels and screenshots from FSX+Instant Scenery-Tests (the same object from different angles).
In MCX I can start and watch the animated light effects: they are wandering from the back to the center...
Could you make are screenshot of a PAPI in a scenery which is exactly working how it should? So I can see the difference?
