-
Posts
1043 -
Joined
-
Last visited
-
Days Won
5
Content Type
Profiles
Forums
Downloads
Posts posted by BenBaron
-
-
Glad you have found an interim work-around that works for you, Ollie. As to why there seems to be some kind of delayed initialization going on for you, I can only speculate for now. I will let you know, once I have given it some more thought .
- 1
-
Hi Ollie,
thanks for your valuable observations...but something really basic still seems to be off: where is the "aerosoft-vdgs-driver.exe" located on your system? As in your xml it states the path should be "C:\MSFS\Community\aerosoft-vdgs-driver\aerosoft-vdgs-driver.exe", but then the vdgs-driver itselfs detects itself running somehwere in "C:\Users\ollie\Desktop\". Then this would also explain, as to why it cannot be auto-started by MSFS...as it is not where it is supposed to be. Also this error is pointing into the same direction: "Airport 'EBBR' COULD NOT be verified, reason: 'PACKAGE_NAME_UNVERIFIED'".
-
Hi Sebastian und Willkommen im Forum:
Die drei benötigten Abhängigkeiten sind in AO unter "Bibliothek" -> "Abhängigkeiten" -> "Optional" zu finden. Wenn installiert dann unter "Installierte".
-
vor 11 Stunden schrieb ollie.j:
It was a fluke. I tried 2x again to start (as admin) and the ability to use VDGS has gone again... Looking forward to the test pat
I tried the new module, but no joy. The log shows INIT when I manually loaded the module after it didn't load using SHIFT+V (not running in task manager). DE-INIT is when I restarted PC. I tried running MSFS as admin and loading it through Xbox app. What next?
Hi Ollie,
in order for the log to show full output, you need to set and save "Verbose=1" in the "aerosoft-vdgs-driver-log.ini". So please set that again. But: right now the module will definitely not work, when started manually. It needs to go through the automatic MSFS startup process for being initialized correctly. So, this is normal behaviour and we need to try and get this running for you.
Please try to also check "Run this program as an administator" for the aerosoft-vdgs-driver.exe.
Startup the sim and once running in main menu, double check in task-manager, as to whether aerosoft-vdgs-driver.exe is running, or not. Might also be running under the FlightSimulator.exe itself. If it is running, load into scenery and try to bring up the ui. In any way, reattach any possible log file.
-
vor 52 Minuten schrieb Ryan E:
Reinstalled scenery seems to be working now.
Hi Ryan,
you mean it is now constantly working for you? If not...please attach a fresh log file again.
-
Hi Ollie,
having the Community folder on C:\ can always cause headaches for programs due to rights issues, where, if an application is running from there, it is not granted all the required rights and fails in some area. Could be that this is the reason as to why the vdgs-driver cannot detect your MSFS is running and thus closes.
I am going to prepare a special test version for you in the next time to try if you can get further with that mechnism removed. Will let you know once I have it ready.
-
vor 9 Minuten schrieb Ryan E:
Hi I am definitely loading into Brussels airport on stand.
Ok...please load up the sim again, load into Brussels and try to bring up the ui. Then, attach the log file again to see if it looks identical to the one you have already provided.
-
vor 10 Stunden schrieb ollie.j:
So, I've tried uninstalling the 3 dependency files, restarting the PC, restoring my PC to pre-20th April, try loading via Xbox, try loading the normal MSFS.exe. The vdgs program doesn't appear in my task manger processes unless I double click aerosoft-vdgs-driver.exe. I've tried setting a different shortcut (followed by restarting sim, etc.) This isn't a great start Aerosoft... how do I fix this? Since reinstalling, my logs are blank - it's like the software never even tries to do anything (or knows it's being asked to do something)... I've tried uninstalling my firewall and antivirus and checking Windows is allowing the aerosoft-vdgs-driver.exe. HELP!
Hi Ollie,
sorry for the problems you are experiencing, but we need to do the problem solving a more orderly fashion in order to really find out what is going on:
On the one hand you say, that the "vdgs program doesn't appear in [your] task manger processes". This indicates, that the autostart might not be properly setup on your system and as the application is not meant to be started manually, this might already be indicative of a deeper problem. So please attach your "exe.xml" file from "C:\Users\{UserName}\AppData\Roaming\Microsoft Flight Simulator" to this thread for me to review.
Then, in the log you provided there is the line "20:24:33 | The simulator has shutdown unexpectedly", which to me looks like your simulator "might" have crashed...at least during that one run? At least the vdgs driver could not find your "Flightsimulator.exe" was running any more and decided it was best to just quit.
-
vor 22 Stunden schrieb Ryan E:
When I click manually to open up the exe app it says its already running then says exiting. But when I press shift v nothing.
Hi Ryan,
the app is not meant to be run manually, so that is normal behaviour.
For starters: you are loading into a parking position at Brussels before trying to open up the ui via LSHIFT+V, right? From the log it seems that after initialization your MSFS is directly sending out a message again that it is quitting (all within ~30 seconds), which makes me believe you might not actually be loading into a flight.
-
vor 26 Minuten schrieb ageva:
I'm getting no UI but the exe is running in the background.
Windows 11 (which might be the issue?). Killing the exe and running as administrator/non administrator/compatibility mode doesn't seems to bring up the UI
Attaching the logs
Thanks,
Amos
Hi Amos,
just to be sure: you are spawned into Brussels airport while you try to bring up the ui? In your log file for some reason there is some initialization missing which should happen once you load into scenery. This would also explain, why you cannot bring up the ui. Don't know why that would be though, yet.
-
vor 24 Minuten schrieb RogePete:
IMHO all this is way to complicated.
Not that I'm not able to understand the procedure.
But do I want another external programm to start with my MSFS (just for parking)?
Another addon fumbling (and breaking) the exe.xml (which was a stupid idea by Asobo in the first place)?
Another setting I have to do before starting my flight?
This may sound much harsher than I mean it. I know the possibilities still are limited in MSFS. And devs have to work with what is in the SDK (and what's not). I just think I won't use the Aerosoft version of VDGS right now. There has to be a way to make things easier / more automated.
Hi,
we have to work with what is there and try to get the most out of it. And surely you can decide, whether you like it, or not :-).
On a sidenote: one of the next steps will be to see if we can get the vdgs-driver refactored as wasm, meaning it can run inside the sim. But in that approach there are also limitations that we have to figure our ways around. So...in the end, its all trade-offs.
- 3
-
Hi Ariel:
as soon as the MSFS Brussels release is out the door, I am going to look into the Mac version again...once I have done that and am in a state to make a reasonable projection, I will come back in here with a status update. I suspect some time in the beginning of May.
Happy Easter!
-
vor 14 Minuten schrieb gaab:
Hi Ben,
I recently used a profile I had updated to erase the " string" specifier on the INT:FCU_SELECTOR vars. The increase/decrease (button 12 and 13) was no more working.
Just "re-introduicing" the "string" for the INT:FCU_SELECTOR only solved the issue.
I confirm that not specifying any unit description for "INT" vars when the value is numeric works correctly.
Regards - Gérard
Thanks Gérard,
will put that onto my list.
Joyeuses pâques.
- 1
- 1
-
Am 10.4.2022 um 14:03 schrieb Dornier728:
The 2.1 configurator was released over a year ago. When will a working Mac configurator be released the Honeycomb Alpha and Bravo if ever?
Hi,
all I can say for now is that as soon as the Aerosoft Brussels release for MSFS with the associated vdgs module went out the door (hopefully smoothly), I am planning to move on to the Mac version, next. Should be this month. And as soon as I see where we stand with that, I will give another update.
- 1
-
Am 8.4.2022 um 13:09 schrieb Ha_Ma:
As i know this is not possible. For the Sim has several online functions it is mandatory that all players have the same version. And this is always the actual one.
Not with the offical versions: but if you choose to enter a SU beta, which is currently running for SU9, you can always go back to the offical SU, this being SU8 right now.
- 2
-
vor 24 Minuten schrieb acbent123:
My flight today was riddled with LNAV issues. The plane either undershot or overshot most of the waypoints and rocked back and forth to the point where I had to diesngage LNAV and go on heading mode and manually get my plane back on track. Can we expect an announcement soon about when we might see a fix? Thanks.
If you are using the SU9 beta (1.25.5.0) we would advise you to go back to the current stable MSFS build. With the beta there is a newly introduced LNAV issue that already got acknowledged by Asobo and needs to fixed on their side.
- 1
- 2
-
vor einer Stunde schrieb Pilotpro1000:
Oh, Great news. May I ask where you got the information from, or do you work for aerosoft - or for limesim?
Just out of interest (with a little curiosity)!keep good work, stay healthy and greetings from EDDB.
..just check out his signature, where it reads:
LimeSim Developer
Antarctica X, Mega Airport Berlin Brandenburg, FTX British Isles, FTX Germany, VFR Germany, German Airfields, Helgoland, LuklaX, US Cities X, Dutch Airports -
I'm pretty sure that the system code will still be WASM based. It was only the EFB that Mathijs talked about being done differently.
-
vor 33 Minuten schrieb JasonmCork:
Is there a break fan on the A330? I thought i heard a Turkish A330 years ago blowing the fan but i remember there is no fan button on AS A330?
Normally you only have those on the narrow body Airbusses...as the wide bodies have longer turnaround times, there is just no need for brake fans.
- 1
-
Am 12.3.2022 um 00:13 schrieb gaab:
Hi Ben,
I am recreating some part of the "default" profiles with the v2.2 Configurator to see how the corresponding .json file is looking.
I noticed that now the "var type" of the INT:vars is no more included and the xxxIsCustom has changed from "false" to "true". I was wondering if there are other changes we should take into account.
So, I think it would be important to get these profiles updated for the new Configurator, as they should be the starting base when creating new profiles.
Is it more clear ?
"Communication is a difficult art"
Gérard
Hi Gérard,
"Communication is a difficult art" ... vraiment :).
Technically, the var type of the INTERNAL variables also does not necessarily be included anymore in the name as the bridge module is trying to infer that from the provided value...which "should" work fine in most cases. If you find a case where it does not, let me know and I will look into it. The xxxIsCustom = "true" change of the Configurator has no effect on the functionality of the profile in sim, but only as to how it is displayed in the ui. If you see any specific problem there...also just let me know.
- 2
-
Am 12.3.2022 um 10:28 schrieb Fatherofsam:
I have a number of issues with 2.10: cannot import profiles; also if I create new profile with copy from default it does not inherit conditional events! Making it fairly useless.
EDIT: I have just downloaded 2.2 again from a link via the configurator software and there are no Mac executable files!
Hi,
please provide specific examples of which profile you are unable to import, or with which profile conditional events are not copied over.
There are no Mac files, as 2.2 is not yet available for the Mac environment.
-
Am 16.3.2022 um 17:08 schrieb Ariel Pinto:
Hi Ben, thanks for your updates, when can we expect a Mac 2.2 version?. Thank you.
Hi,
right now my goal is to move on to the Mac version beginning of April. I will keep you in the loop as to how it goes.
-
Hi,
I've have moved you into the correct X-Plane subsection of our forums which is more appropriate for those kind of simulator specific questions.
If you check out the provided "Default_Throttle" profile, you can see that you have to indeed provide the value "1". Otherwise, how would the system know which state of the datatref signals the ON state of the LED?
-
Thanks Gérard for your input...I am going to note your suggestions...but honestly I am not 100% sure I am getting what you mean by that part:
Am 7.3.2022 um 23:13 schrieb gaab:It would also be great to get the default profiles with the "new rules". I discover that now the "string" type is no more specified AND the VariableIsCustom is "true" when created with the Configurator.
In the included Default, they are specified as
"Condition": "INT:FCU_SELECTOR, string",
"ConditionValue": "ALT",
"ConditionIsCustom": falseand
"Variable": "INT:FCU_SELECTOR, string",
"Value": "IAS",
"VariableIsCustom": false,
Both seam to work, but this creates some doubts...
Maybe you can elaborate a bit more?
And the wrong version in the "About" dialog is also confirmed as a small bug.
Can't get the VDGS to work with Brussels
in Aerosoft VDGS
Posted
Thanks Andy for the report as well: once I have a version ready to test that uses a different initialization structure I will let you know in here.