!! Windows 7 no longer supported !!

As Microsoft will stop supporting Windows 7 on Jan 20th we will be unable to test any of our
products on that platform. It may work, or it may not, but no guarantees from our side. 

Jump to content

Michael2

Developer
  • Content Count

    483
  • Joined

  • Last visited

  • Days Won

    1

Michael2 last won the day on April 13 2018

Michael2 had the most liked content!

Community Reputation

226 Excellent

1 Follower

About Michael2

  • Rank
    Gliderpilot

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. Did you go back to 2.0 and find it works again?
  6. You could save a flight cold and dark and then open it and move the aircraft to whatever airport you want.
  7. 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.
  8. 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.
  9. 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?
  10. 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 .
  11. 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.
  12. 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.
  13. 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.
  14. 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.
  15. 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.
×
×
  • Create New...