Jump to content

Tom Gibson

Registered Users
  • Posts

    170
  • Joined

  • Last visited

  • Days Won

    1

Tom Gibson last won the day on February 11 2023

Tom Gibson had the most liked content!

4 Followers

Recent Profile Visitors

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

Tom Gibson's Achievements

Community Guru

Community Guru (4/7)

  • One Year In
  • Reacting Well Rare
  • One Month Later
  • Conversation Starter Rare
  • Week One Done

Recent Badges

32

Reputation

  1. Warnings do not cause compile failures. Look for Errors instead. If you cannot display the building in MCX it may be that there is something incompatible with an FS compile?
  2. If you can't pinpoint it, disable all addon scenery in the Scenery Library and then check again. If that fixes it, then activate half of them and try again. Continue by dividing and checking again until you find the culprit.
  3. The maximum compression can be determined by using ModelConverterX, assuming you don't have the source code for the model. 1. Import the plane of interest. 2. Open the Hierarchy Editor, check the Highlight Selected box, and look through the parts on the left for the landing gear. I do this in wireframe view which is the easiest to see. 3. When you find the landing gear (we'll use the right main gear as an example) look for a SceneGraphNode or ModelPart that uses the animation r_gear (in this case, other choices are l_gear and c_gear) and the animation type is Position. Make sure the part/Node is highlighted as selected. 3. On the right side right click the word Animation and choose Edit Animation. 4. In the resulting dialog box look for keyframes 100 and 200 - between the two that is the maximum compression. 5. Take the numbers in the Y box for the two keyframes and subtract one from the other. This would give you the maximum compression (mine is in feet, I don't know if that depends on your MCX settings). From this value and the Static Compression value in the aircraft.cfg file you can calculate the needed Compression Ratio. If you change the Static Compression value you will also need to recalculate the Compression Ratio. As an example my flyable DC-6B has a Maximum Compression of 1 foot. If I would set the Static Compression at 0.8 feet, then the ratio would be 1/0.8 = 1.25. I typically set the damping ratio to 0.9 or higher (max = 1).
  4. Glad to help, I should have thought of that solution too.
  5. The only way I can think offhand of how to fix this would be to make a gauge with that area of the panel background displayed, and sequence it after the wiper gauge. If there are any other gauges there, they would have to be sequenced after the panel background and wiper gauges.
  6. How does it work in the IL62? Does it actually drop down behind the main panel when it moves?
  7. Oh, I didn't know that Aircraft Container Manager could load scenery MDL files, sorry.
  8. FS Repaint could also do this. An old Abacus program, as I remember. No longer available, I assume. And ModelConverterX can be used to view the different liveries. The latest development version will allow you to use the green arrows to step through the various model folders, and with a model loaded you can use a drop down box to view all the liveries. You can also switch between the FS9 external model and the VC using a drop down box. If you load the aircraft.cfg file of an FSX or later aircraft you can do the same thing. And you can change the Options/Importer Settings/Use Conditions to VisibilityCondition and avoid that box that pops up with FS9 models to specify visibilities. Note however, that while Arno is working on it, exporting FS2004 aircraft is still not perfect, nor is conversion from FS9 to FSX (or later) aircraft. Getting there, though!
  9. As a plane builder, there is little we can do. If there is a Z-buffer issue it is usually parts of the plane that disappear behind the blurred props. That we can usually fix. Generally we have little control over whether clouds and other effects can be viewed through them. That said, using FS9 aircraft in FSX will certainly cause this issue, and can be avoided by converting the plane to FSX format.
  10. Glad you are doing better, we're all glad to hear it.
  11. I think it is an issue with some video cards or video driver versions. Not much you can do?
  12. While this is probably due to a windows update, usually the solution to that Administrator problem is that you need to run the noCD patch. Are you trying to run it with the FS9 CD in the drive?
  13. If nothing happens when you start FS9 check this: https://calclassic.proboards.com/thread/7470/fs2004-start-read
  14. Not that I know of.... But I don't do much photo scenery.
×
×
  • Create New...