Jump to content

Michael2

Developer
  • Content Count

    515
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Michael2

  1. Thanks for the feedback!
  2. Are you sure these sounds are from the DC-8? I'll look, or rather take a listen, but I have never noticed this before. Possibly the sounds are from an airport addon? I know I have some that make a lot of noise.
  3. I will take a look at this. During development I used the recommended cruise altitudes in the performance document and typically did not use loaded weights low enough to get into FL370 or similar.
  4. Michael2

    Loadplanner

    P3D v.5 is not supported as has been discussed here previously.
  5. The altitude selection is only a memorandum of your assigned or desired altitude and also gives a warning when leaving or approaching the altitude. The DC-8 autopilot doesn't have an altitude capture function. Instead, as you approach the desired altitude you should reduce your vertical speed and then set it to zero when you reach your target altitude.
  6. Sorry the delay in posting and getting the new FSX version out. I have been out of town a great deal (locally) and away from computers. I'll get the FSX new version to Aerosoft this week and look at any support issues I see on the forum.
  7. Not yet. I should get the files to Aerosoft early next week.
  8. You're very welcome. I'll get the FSX version ready now and we should get it out soon.
  9. He's certified and ready to go. The installer (for P3D) is tested and I expect it will be available for download soon, but given the time zones and weekend, not today. This update will be a re-install rather than through the updater. So you will need to back up your liveries and aircraft.cfg file.
  10. Rainero, I can understand that you're disappointed. I'm sure it's a difficult choice for everyone whether to move on to P3D v.5 or not. Some products are going to be going to left behind in going to v.4.5, not just the DC8. I did consider a paid update, but in my opinion it wouldn't make sense. As everyone knows, a new Microsoft Flight Simulator is coming and I don't see much future for P3D addons when it arrives. I could be wrong, but that is what I think will happen. Hopefully the new sim will greatly expand the customer base for flight sim products generally. To make even a paid update for P3D I believe I'd be making a low rate of return on my work even lower. I think it makes more sense to develop for the new sim which will hopefully provide a stable platform without constant breaks in compatibility, and many more users. For the time being I'm still going to stick with steam gauge airliners -- a decision that will probably benefit those who like those products a lot more than it will me. Meant to say "in going to v.5". There doesn't seem to be any way to edit my posts.
  11. As far as I know, FSUIPC will only save default variables. The INS has many custom local variables. The aircraft comes a special Aerosoft module to save the local variables when you save a flight, but it doesn't have an autosave function.
  12. Sorry guys, there were a couple of files missing from the update. They have been sent to Aerosoft just now and should be available soon. We'll announce it here when it's ready. As for P3D v.5, as far as I could see it works, but to me there are significant issues with how it looks. The textures are rendered with very high contrast. For the aircraft to look as intended, I would have to redo the aircraft with PBR materials and I just don't think the amount of work is justified when I consider the number of units sold. So the product will remain a v.4.5 product.
  13. No, I don't believe there is any way to start the INS in flight and have it aligned. I didn't code the INS myself, but I don't recall there being any feature of that kind during development. Of course, if you are having frequent CTDs, you can always manually save the flight during cruise and all the INS parameters will be saved.
  14. The only other possible cause I can think of is the custom lateral autopilot when the autopilot is set to AUX, in other words when the INS is controlling your heading. I know that some weather settings can cause what I experienced as a minor fluttering of the ailerons on one or two occasions during development of the aircraft. Can you check in the outside view when this happens and see if the ailerons look as if they are fluttering or vibrating?
  15. The next version of the DC-8 for P3D v.4.x is complete and will be available soon. The same will be available for FSX shortly thereafter. You will find it has an option to use an automated flight engineer. To use the automated engineer, you will still have to do everything yourself up to configuring the FE's panel for takeoff. You will have to remember in particular to set the cruise altitude in the cabin pressure part of the panel. Then, shortly after you advance the throttles to begin your takeoff run, the FE will go to work and you will hear a series of clicks from time to time as he works the panel. All functions are automated -- he will even turn on deicing when needed. You will have to tell him, however, when you are beginning your descent and the altitude of the destination airport. After landing, and taxiing to the gate, you will need to shut down all engines except #3 after which ground power will connect automatically and the FE will select ground power on the panel. Then #3 can be shut down. You will also need to set the parking brake at the gate to trigger further FE actions. There is also a slight improvement to the altitude hold performance in turbulence at slow speeds.
  16. Very likely this is a faulty or missing XMLTools install. XMLTools is a module that allows various custom behaviours that aren't possible with a default aircraft. See the thread referenced below for details and be sure to post again here if that doesn't sort out the problem:
  17. There isn't anything like that. Some of the default keys may work, but I haven't tried this myself.
  18. Does the GTN 750 control the autopilot? I'm not familiar with the product. The DC-8 has a blend of custom and default autopilot functions, so it may not work well with add-ons that control the autopilot.
  19. I have a new build ready that makes a slight improvement in this. I just need to test it a little more and package it for upload to Aerosoft.
  20. I can't reproduce this. Are you on P3D or FSX?
  21. I've made some changes that should bring some improvement -- I'll try to get a new version out soon. You would think I would have a lot of time available in the current situation but in fact having my kids out of school and trying to manage their online alternative has had the opposite effect. I have never noticed any instability with the altitude hold at cruise -- only during the approach phase when the aircraft is flying at 250 knots or less. I don't use Active Sky which may be why I'm not seeing the same thing some users are. For some years I've used Opus for weather.
  22. You just need to find the switches. There are a number of light switches on the overhead, one of which is marked for the pedestal -- that's for the integral back lighting. There is also a floodlight switch on the ceiling further back that lights a red floodlight for the pedestal. For the engineer's panel you've got two working light switches, one marked INST PANEL WHITE and another marked WHITE FLOOD.
  23. Hello, sorry you're having problems with this. The cause is almost certainly a bad install of XMLTools. I removed the dll from my root folder to test and the result is as you describe -- you can't change the cargo values and the fuel numbers change but don't actually do anything since the weight remains the same. You need not only the dll in your root P3D folder but also the correct entry written in your dll.xml file. This file should be at the following location (taken from my setup): C:\Users\Michael\AppData\Roaming\Lockheed Martin\Prepar3D v4. Here is the text from my dll.xml file: <SimBase.Document Type="Launch" version="1,0"> <Descr>Launch</Descr> <Filename>dll.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon> <Name>XMLTools64</Name> <Disabled>False</Disabled> <ManualLoad>False</ManualLoad> <Path>XMLTools64.dll</Path> <DllStartName>module_init</DllStartName> <DllStopName>module_deinit</DllStopName> </Launch.Addon> <Launch.Addon> <Name>FSUIPC 5</Name> <Disabled>False</Disabled> <Path>C:\Program Files\Lockheed Martin\Prepar3D v4\Modules\FSUIPC5.dll</Path> </Launch.Addon> </SimBase.Document> Ignore the entries related to FSUIPC, but make sure you have the rest. Either the installer couldn't find the file, or perhaps another addon corrupted it. Let us know if this information fixes the problem for you or if you need further help.
×
×
  • Create New...