aivlasoft
-
Posts
5,910 -
Joined
-
Last visited
Posts posted by aivlasoft
-
-
Sorry for the late answer. I have to dig for the source code and will let you know about the result.
-
Thanks for uploading the files. From the DatabaseBuilder's logfile I can see that only 980 airports (instead of approx. 25'000) have been found according to the different add-on.xml files and scenery.cfg. I must assume that something went wrong when you updated your P3Dv5 installation.
-
Could you please create a set of support files, one from the Server and one from the Client. Please upload them here for further investigations. Thanks.
-
You will find all the required information and links here: https://www.aivlasoft.com/
-
Have a look at these screenshots.
1) KCLM ILS08 via JIGEB:
This is a good example for so many approaches, especially in the US where you fly over a VOR or a fix, then outbound to another fix where you make a procedure turn and then fly back the same way again. Here you have to pass the waypoints in the red circles twice. If the 'logic' were taking just the closest waypoint, then all the waypoints after ELWHA were being considered as passed as soon as you pass ELWHA for the first time.
Another example where taking only the closest waypoint could lead to unwanted effects. Approach EDDS ILS25 via REU25: While on the northeast leg (068°) passing IBIRU, or later at DS522, the waypoints on the 'other side' are too close to get activated, especially when you don't fly accurate enough on the desired track.
From my point of view there is no reason to change the currently implemented logic. It works for a vast majority of situations, and for all not covered cases just use the DIR-TO function to sync the flight plan.
-
13 minutes ago, Berzerker said:
That's my point, I think it should not have that requirement. If you pass directly (or within 3nm) of a waypoint, it should update no matter what you've passed before. I can't think of a situation where when you're passing within 2-3nm of a waypoint means that's not your current DIR and it shouldn't update.
Especially on certain (RNAV-) approaches this will not work because the waypoints are too close to each other. That's the reason why the requirement was implemented that all waypoints before must be passed. Otherwise the sequence might get a hick-up.
-
2 hours ago, Berzerker said:
If you pass directly over a WPT or at least within a few NM (1-2nm), it's clear you were DIR that WPT and it should auto update
This is the logic which is implemented already. A WPT is considered as passed if you fly over or by within a range of 3 NM. However, the condition is that all waypoints before must also be passed.
2 hours ago, Berzerker said:Inputting an approach after already being on the arrival/having input the arrival should put you back on the previous DIR WPT you were on before you input, not back to the beginning.
Changing an arrival and/or an approach when you already are on this arrival or approach will always cancel the above mentioned logic because changing an arrival and/or an approach will change/remove multiple waypoints in the flight plan and therefore the logic must be manually reset. If you change your flight plan you always have to use the DIR-TO function to re-sync the logic with your current flight plan. There is no other way to accomplish this.
-
1 hour ago, Berzerker said:
Just trying to throw out some ideas.
That's fine, thanks.
Just a few thoughts from my side as the programmer. To implement a logic in a program one requires that clear and unambiguous rules are available, which this logic must then strictly follow. I think that there are a lot of different possibilities in the situations described above, so that it is almost impossible to identify all cases and to determine an appropriate set of rules from them.
Not always every situation can be solved with a program (at least not with reasonable effort), therefore the DIR-TO function was implemented, which allows the pilot to make its decisions based on his experience and the situational awareness and then to act accordingly.
-
Sorry, my fault. You're right, the path cannot be indicated because the file isn't recognized. Look for the respective airport folder in '..\official\onestore'. If you have located the folder, look for the folder '..\scenery'. There you should see the airport file having a postfix '.fsarchive'.
-
Unfortunately we do not have this airport in our collection. You can check in the installation path (path should be mentioned in the 'i'-window of the airport) whether the file type is '.fsarchive'. If so, the airport data is encrypted as I mentioned above.
-
Thanks. Standby ...
-
Unfortunately airports which have been purchased through the in-game-marketplace are often encrypted due to copyright reasons. Such airports cannot be read by EFB (see restrictions). I don't know whether this is the case for the airport that you are talking about. Can you provide the ICAO code and the developer?
-
46 minutes ago, Berzerker said:
Would it be possible to add in some logic on the backend that handles situations where if you forget to set a DIR after being given one, it never updates your flight plan once you reach subsequent waypoints?
If you forget it, how shall the software know about it? I guess that this is not possible.
46 minutes ago, Berzerker said:Also, when adding in an arrival, or updating an arrival, it always seems to set your Active WPT to the first WPT in the arrival/approach, it would be good if there was some logic to recognize which one you're inbound to or near, or perhaps to update it once you pass over the next one to know which your Active WPT truly is.
Why not just use the DIR-TO function in such a situation? If programmable at all, such a logic would be far too error prone.
-
The values for speed are taken from the output of the simulator. There is not much we can do in this regard.
-
Hi Rene
you can use the same installation for all simulators, but you have to create a database for each simulator first. Then, to switch from one simulator to the other, just change the database. You can do this by selecting the required database in the DatabaseBuilders dialog. Please see the manuals, thanks.
-
What kind of data format (which program creates it) do you mean with .fpl ?
Did you already have a look in the manual "6 EN Flightplan.pdf" ? There are several options to load a flight plan into EFB.
-
P3D requires FSUIPC, as described in the manuals.
See also here: https://forum.aivlasoft.com/topic/7783-incorrect-airport-on-startup/
-
1 hour ago, Terblanche said:
Also, after latest update for Client & Server there is also a XP database (and I don't even have XP) and it doesn't matter how many times you click 'DELETE' it simply won't go away. Thankfully it reads from MSFS database that is selected.
Please see the updated announcement here: https://forum.aivlasoft.com/topic/7787-update-23-140/
-
On your screenshot I can see 'Airfile name: 737'. Did you already try to add '737' to the list of Airfile names in the profile of your aircraft?
-
This seems to be a commonly known issue with certain aircraft. Did you already use the search function of this forum? I'm quite sure this has been answered several times already.
-
Could you please provide a screenshot which shows the error? Thanks.
-
v2.3 #140 has been released today.
-
Today the new version 2.3 #140 has been released.
Among some minor bug fixes, it contains the integration for Prepar3D v6.
EDIT: 2023-07-22, 19:45z:
We had to stop the Auto-Update for this latest build because there is a bug which mixes up the existing databases.
We apologize for the inconvenience and will fix it asap.
As a remedy for this, please do the following steps:
- Quit EFB Server and/or DatabaseBuilder
- Locate the folder 'C:\Users\<username>\Documents\AivlaSoft\EFB2\Server\DbBuilder\Ready' (default installation path)
- Delete the entire folder
- Start the DatabaseBuilder and create the EFB database(s)
EDIT: 2023-07-23, 07:17z:
Issue resolved. Auto-Update is back to normal.
-
Assuming you have the technical data from your aircraft you will use the Profile Editor. Please see the manual "5 EN Client.pdf", chapter 12.2 "Profiles editor"
SimpleCam für Prepar3D v6
in SimpleCam v1 - Support forum
Posted
I have found the source code. So far so good. But it will be difficult to implement the required changes because I have no longer a license and also no longer a P3D installation on my system anymore. Would you be ready to do some tests when an updated version would be available?