DocFlying

Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

0 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No
  1. Problem solved. Had an issue with my router firmware. Everything works fine now (despite the known problem with the water shaders ;-) ). Thank you Matt for your reply. You did a great job. This tool is more than helpful. I do even think about doing without adon sceneries.
  2. Yes, i am running as admin, internet-connection is checked, firewall and av-software switched off, p3d and pta reset and restarted several times,
  3. Same for me. Activation worked once. Now opening the program always leads to an error "activation neccesary", trying to activate again fails with "server error". Is there any support for that software?
  4. DocFlying

    LINDA and WideFS

    Hi, i am running a selfmade A320-homecockpit with FSX on a Win7 - 2 PC-System, FSUIPC, WideFS, Arcaze-USB-Modules, LED-Drivers and display-Modules. Due to performence problems i connected 3 of my 7 USB-Devices to the second PC (not running FSX) and connected them via WideFS with FSUIPC. I defined all Buttons, Switches and Analog-Devices in FSUIPC, using the FSX-Controls and FSUIPC-Offsets spending a lot of time including programming some LUA-procedures and editing the FSUIPC.CFG. Everything is running fine with the standard FSX-Airplanes and i am very grateful to all the providers and programmers of the different peaces of software for enthusiatic flight simmers. They are doing a great job! Now my problem: Since the default A321 in FSX is not very realistic and lets a lot of features missing, i want to change to the new aerosoft airbus A320/A321. I already downloaded it, it works and looks very professional, but about 80% of my hardware doesnt work any more, since aerosoft doesn't use the standard controls and offsets of FSX. This could be solved by using LINDA additionally and redefining all the buttons and switches, which i am willing to do for the benefit that aerosoft offers. So i downloaded and installed the newest version of LINDA and the aerosoft airbus 4.3 v2 modules. So far so good - LINDA synchronizes with FSX, recognizes the aerosoft airbus but only those USB-Devices that are directly connected to the FSX-PC. I can program their buttons, but LINDA does not find the USB-Devices whitch are connected via WideFS. They are still persent, when i open FSUIPC itself but not via LINDA. Does anybody work with the combination of LINDA and WideFS and is there any chance to program the "satellite-" buttons? I hope i can find a solution because FSX slows down tremendously when i connect all devices to the main PC. Thanks for any hint or help. Uli
  5. DocFlying

    Pactice patterns with VOXatc?

    Hi Mad Mac, yes, i agree, VoxATC is by far the best peace of software for offline ATC. So we all hope, that Tegwyn will publish an update soon. Uli
  6. DocFlying

    Pactice patterns with VOXatc?

    Thanks for your advice. I tried it and indeed - it worked. I just never used the words "... this time" before. Sometimes not easy to find the right phrase. Do you know if there is any tutorial especially for VoxATC phrases? Or is there any file which contains a list of the mandatory words for the different situations? I already analyzed the html-files in the VoxATC folder but they list only part of the phraseology. Thanks again Uli
  7. DocFlying

    Pactice patterns with VOXatc?

    There are several posts dealing with patterns or circuits in this forum but this is the youngest one. So i try to get some help for my problem here. I am using VoxATC with FSX and my homecockpit after a bit of experimenting very successfully and had some very happy flights and landings. But i am still working on one problem: When i practice local patterns (or circuits) i never get a clearance for a full stop landing but only for touch & go. I tried each and every phrase in the different legs of a pattern (downwind for full stop (landing), request full stop (landing), on final for full stop (landing)) but allways the same, either "say again" or "unable at this time". The funny part is, that after clearence for touch & go VoxATC orders (in red letters) to "taxi clear of runway" as soon as i touch the runway. But when i do this no choice to report "vacated runway" or "request taxi instructions or taxi to park". But - the runway keeps blocked for other traffic, regardless if i taxi off the runway or perform a real touch & go and rejoin the pattern. Anyone any idea what i am doing wrong? Thanks, Uli
  8. DocFlying

    anyone running version 6.49?

    Hi, You can download the older versions via the following .net-adress. For Version 6.49 choose www.voxatc.net/649/ Regards Uli
  9. It is not even completely useless in non-default aircraft. MCE lite doesnt run any more as soon as you change any detail in the data set (for example panel.cfg or gauges) of the original FSX aircraft. Look at the respective topic "MCE lite" of johnbla in this forum.
  10. DocFlying

    MCE Lite

    I am not interested in a formal complaint to Avsim. I allready followed your advice on your Home page: "Please note that like any software package released, some users may run into some issues that we could not foresee. But our team will be more than happy to address them. All you need is e-mail." Your answer to my complaint was: "Because there is a risk people may masquerade one particular aircraft for one another, the Lite Edition is just that." So in your eyes every customer at first is a cheater and not someone who believes your announcements. The comparison table on your home page (http://www.multicrewxp.com/CompareEditions.html) says for the lite edition: Supported Aircraft: Default FSX & FS9 aircraft only Supported ATC: Native FSX and FS9 ATC to be used with Default aircraft only No hint at all, that simmers are not allowed to customize the default FSX aircraft in the tiniest detail. Just imagine, you by an original car, mount a new steering wheel and the engine stops running becaus its no longer the original car. funny, ha? Nice idea. But how do i know, that the review copies are the same as the edition that i bought. "Because there is a risk people may masquerade one particular software for one another." Thats what i learned after buying the lite edition. As i mentioned: No hint of that kind on your home page. So, i am not discussing tiny details any more. Just wanted to give people, who think about buying MCE lite edition, a hint by reporting my experience with the software and the support of FS++. Nothing to add to the comments under this topic so far. I deleted the lite edition from my system and will look for a better solution. VoxATC seems to be an alternative and a fair one. Even if i'd receive the MCE ultimate edition as a present, i would'nt use it because nobody can tell me what kind of other tricks were waiting for me.
  11. DocFlying

    MCE Lite

    Its not a false statement at all. Editing the original cfg-file by only changing the call sign of the original AC lead to a stop of MCE lite on my system.Again: I AM using the original FSX A 321, just with a modified panel.cfg and gauges for correct displays on my multi monitor system. This is definately NO other AC! Stating that i am trying to betray with another AC is more than strange. The demo worked perfectly with my system and the modified FSX A 321. The problem started AFTER i bought the MCE lite version. Just think of your selling strategy and people will stop complaining.
  12. DocFlying

    MCE Lite Edition has been released

    Beware of MCE lite! It purely runs with the untouched original FSX AC. You are not even allowed to change the panel gauges, for example for a multi monitor home cockpit. MCE will be fully stoped with the message "you are running the wrong version". Even changing the call sign of an original AC might kill MCE lite. So: Hands off! You will loose 20 bugs for nothing!
  13. DocFlying

    FSX voice interaction

    Hey Ernie, if you are still thinking about the lite version, keep hands off. They say that the lite version supports all original FSX Ac, but they do not say that you are not allowed to change any data of the original set. So if you want to change the gauges for a multi monitor display in a home cockpit, MCE lite will be fully stoped. Even the change of a call sign might kill MCE. Therefore i kicked it off - lost 24 Euros for nothing. Uli
  14. DocFlying

    MCE Lite

    Yes i can confirm that. And even worse. Not only that it only works with original AC. You are not allowed to change any of the original data. Even changing the call sign of the original FSX AC will lead to a note, that you are running the wrong version and will fully stop MCE. Conclusion: Hands off!