Support overload. We are currently seeing 65% more demand for support then we normally see. We can only assume this is because more people are at home due to the corona crises. Our complete support staff is online and they are working flat out, but it will take some days before we can scale up resources. Please be patient.

Jump to content

Michael2

Developer
  • Content Count

    492
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by Michael2

  1. 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.
  2. 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.
  3. Seems to be a double post. I answered in the other one.
  4. I'll look at this again. I made a change to get more realism in another area and the AP porpoising in some conditions is the result. There is some code to mitigate the behavior, but maybe I could find a better solution. We'll see.
  5. You would only use them if you had inadvertently messed up fuel management so as to create an improper distribution of fuel or in the event of a failure that required a non-standard fuel configuration. For example if a main tank was leaking or couldn't fuel and engine and you were still transferring from the centre tank you would close the main fill valve and open the alternate one while feeding the engine from the alternate tank.
  6. I believe we have three users reporting this and it now seems it cannot be linked to FSX non-acceleration as one user reports it occurring in P3D 4.5. Apparently it only occurs with the DC8 v. 2.1 but not 2.0. Since the problem is not general to all or even many users and since I have never been able to reproduce it in FSX or any verision of P3D (I am now on 4.5), I am not optimistic that a solution will be found. A new version will be coming out soon -- we'll see if the problem is still present then.
  7. There was a problem identified with the hydraulic problem and a fix was implemented in version 2.0. There was another thread about this in which one user reported continuing problems. He wrote: It seems to possibly happen if you set the plane to Cold & Dark and then move its location to a different gate or airport. Is that a possible factor in your case?
  8. That should have been deleted from the checklist. The real aircraft has a small panel with a couple of switches stuck onto the side of the lower engineer's panel which I have not simulated.
  9. Did you install XMLTools during the install process? The load manager and many other features won't work without it. Does it load fuel?
  10. I'll have to leave you in suspense for a while as I don't want to start a discussion about it until I have something worth showing. All I will say now is that it's a steam gauge era airliner.
  11. It's on my list for the next update. The cause is very simple. I forgot to make the light and sound conditional on having electrical power available. I overlooked it probably because it's not standard equipment and therefore not listed for any electrical bus in my manuals. I'll choose a bus that seems appropriate and make the change.
  12. I think just for MSFS. If I were to make a P3D version, MSFS would probably be released by the time I'm done and I doubt many would buy it for P3D then. Also, I suspect it would be a huge amount of work to put an aircraft in both sims as I think there will be significant differences in how aircraft are best made for each. If I had something almost ready for a P3D release, that would be different, but it's not the case - still quite a ways to go.
  13. OK, you can edit a file to do this. It appears to do what you want, but this will be unsupported in the event there are any problems. Open the logic.xml file in the panel\DC81 folder. You can use Notepad, but Notepad++ (freeware) is better. It might look garbled in Notepad. At the top of the file you will see a section labelled initial load. Then there is a long list of items contained by curly brackets. At the very end of that, right before the closing bracket, add the following line: 1 (>L:DC8_cold_dark, bool) It must be after all the other items. It's just one line, so it's easy to remove or add back if you wish. After the next update it will likely get overwritten, so you will have to add it back after updating.
  14. Did you go back to 2.0 and find it works again?
  15. You could save a flight cold and dark and then open it and move the aircraft to whatever airport you want.
  16. It shouldn't do that, but I will take a look. In the meantime, try setting the value to something more than 1000 feet above the airport altitude to put it out.
  17. I am working on something for the new MSFS (initially it was to be for P3D), but it's too early to show anything and the SDK is not even available yet. Given your suggestions, I think you would be reasonably happy with my choice.
  18. dcon: Can you clarify? It was OK on FSX SP2 until you updated the DC-8 to v. 2.1? V2.0 was OK? They eventually fixed it for non Acceleration users. Thanks for pointing that out, I had overlooked that post. But he says he was OK until v. 2.1 if I understand him correctly. And you have the same problems with both 2.0 and 2.1, is that right?
  19. I know this is not a proper solution, but ... One way to get you flying is not to use VS. Instead, when you turn on the AP, turn the pitch knob to PITCH DAMP and then control your VS with stabilizer trim until you get to cruise altitude. I just tried this and it's not very different from using the VS wheel. Also, I would be interested in knowing if it stops the shaking. As for shaking on the ground, try loading the aircraft before doing anything else to see if the weight stops the shaking. Also, the aircraft loads with the INS aligned -- you don't have to go through that manually. I don't like to suggest workarounds -- I would prefer that you be able to use the product as intended, but right now I can't think of anything else that could cause the problems you are facing .
  20. One more thing -- don't use any key commands for AP controls. Only use the 3D or 2D controls in the DC-8 product using your mouse. Using keys for default AP commands could mess things up.
  21. I discovered the Captain Sim AP issue relates to an AP pitch hold variable that the DC-8 doesn't use, so that isn't the problem.
  22. Well Craig, I am running out of ideas. There isn't anything for me to fix, since I can't duplicate the problem. I looked over my code for the vertical speed AP function. It's a mix of custom code and default autopilot, mostly default. It does use XMLTools, so it's important to check that you have the entry in your dll.xml file. That file can be messed up by other addons. Just because the installer ran doesn't mean it's properly installed indefinitely. Make sure you check the file and also see that the XMLTools.dll is in your root FSX folder. The SP2 vs. Acceleration issue does ring a bell with me now. I seem to recall that the VS didn't work on the Captain Sim 727 without acceleration because it used a new variable introduced with Acceleration. I'll try looking into that, but there surely must be other DC-8 users who don't have Acceleration, so I doubt this is the issue. Finally, I suggest going into your FSX control setting and select the autopilot event category. Make sure there are no AP functions mapped to keys you may be using for other things.
  23. We should make sure XML Tools is properly installed. Can you check the dll.xml file and see if there is an XMLTools entry? Without XMLTools installed, many aircraft systems won't function correctly. On my system it's located as follows: C:\Users\Michael\AppData\Roaming\Microsoft\FSX\dll.xml . You can open the file with notepad.
  24. The P3D and FSX versions have exactly the same systems coding and flight model data. There is no difference as to how they perform in the sim. The P3D version has some different lights and the VC textures were darkened a little as they get rendered differently in P3D. Also, the FSX logic coding is broken into 3 files whereas in P3D it's in two files as the two sims have different maximum gauge file sizes. FSX Acceleration introduced a better drag rise due to mach table, so if you don't have Acceleration, you may find the EPR cruise setting don't give you exactly the correct mach speed, although it should still be close - - not way off as you are describing. By the way, you should know that the aircraft has realistic icing simulated. If you fly in icing conditions ice buildup will progressively cause increased drag and a loss of lift unless you use the deicing system on the FE panel. When it's on, the effect of icing will gradually dissipate. In terms of cabin altitude, are you sure that the low pressure manifold switches and cabin compressors were turned on? The product has been out for some time and there are many people using the FSX version and no one else has reported these issues. So it must be something unique to your install and setup. The fact that you a using the mouse as a controller is interesting -- I have never done that so I will give it a try to see what happens.
  25. I just did the tutorial flight takeoff and climb out on both 2.0 and 2.1 in FSX. I had no problems with the AP on during the climb at all. So I think it must be your weather program, some other addon that tries to fly the plane, or a controller issue that is messing with the flight controls, trim or AP. Again, the weather program I can't rule out until you test aircraft without it running. I do now recall shaking during development (well before beta testing) at one time when the aircraft was in the AUX/INS lateral mode and I was using some version or other of the OPUS weather program. The INS uses custom AP coding and I remember it didn't work well with the weather program for a couple of flights and then it seemed the problem just went away. What lateral mode is selected when you turn on the AP? However, I recall it didn't affect pitch. It just caused the ailerons to flutter and when it got bad the aircraft was more or less shaking. Maybe you could make a brief video? If you have windows 10 you can do this with the Windows key + G.
×
×
  • Create New...