Jump to content

miatamariner

Registered Users
  • Posts

    245
  • Joined

Everything posted by miatamariner

  1. Thank you Mike. I was not aware that you could install Steam games to another drive while still having the main program on the C drive. My SSD is drive E. Can you tell me what a path would look like for a Steam game, say FSX, on my E drive?
  2. I am considering purchasing MSFS2020 through Steam. I currently have FSX installed to a SSD to where I would also like to install MSFS2020. Does Steam allow installation of their base program to a drive other than C:\Program Files(x86)?
  3. I can't believe that LR doesn't have the capability to simply provide an option to couple the rudder to either banking or roll modes to allow simple nose wheel steering.
  4. My first foray into X-Plane and 12. I have the Saitek Yoke and throttle quadrant, but no rudder pedals. In FSX, there is an option in flight controls to activate automatic rudder control. I've searched the Settings menu and Flight Controls but can not find a setting to couple the rudder control to the Yoke, to keep the aircraft from moving left or right from the centerline, on takeoff. Is there a setting to do this?
  5. Every time you change a co-ordinate numerical value in the "window_pos" line, it will change the position of the gauge on your panel, so yes, to move it to a new position, you need to change values. It is a trial and see method.
  6. Go into the panel folder of the aircraft and then open the panel cfg file. Find the Window for the Throttle Quadrant. It should look like this. xx being the number of the Window. [Windowxx] Background_color=0,0,0 size_mm=265,414 position=8 visible=0 ident=1030 gauge00=B737_800!ECU, 0,20,265,394 Find the line "position=8" (no quote marks) Remove just the number 8 so it looks like this. position= Under the "ident=1030" line, add the following two lines: window_pos= 0.000, 0.000 window_size= 0.265, 0.394 In the window_pos= line, change the first set 0.000 to 0.300. This will move the gauge to the right. Change the next set 0.000 to 0.400. This will move the gauge down. I'm only using these numbers as examples for you to see how the position of the gauge has now changed. Now save the changes. (Ctrl + S). You can do the same for the window_size= line to change the size of the gauge.
  7. My very first flight sim! I remember marveling at the quality of the clouds and flying the CJ. Wish I still it just for a reminder of where we were then and where we are now.
  8. I just can't win! Tried to attach the file but Flightsim says it is an invalid file. So how come it is in the Library? At any rate, here is the the Installation and Description text file, written by OPA. Modified language.dll for FSX - ENGLISH Version ONLY. 1. In your main FSX folder, find and rename the present language.dll as language.dll.Original 2. From this package, Copy the replacement language.dll from the folder named Edited Language.dll and Paste it into your main FSX folder, replacing the one you just renamed. 3. Start FSX and you will have modified Brake and Overspeed messages. The Brakes message will now display as B The Parking Brakes message will now display as PB The Differential Brakes message will now display as DB The Overspeed Message will now display as OVSP To restore the original file, delete the replacement and restore the name of the file you changed in step one. A copy of the original default language.dll is included in this package in case you should need it. TECHNICAL NOTES: The language.dll files were modified with a program named Resource Hacker which can be download from: http://www.angusj.com/resourcehacker/ The modification to the language.dll file affect all aircraft of course. To simply change the speed at which the Overspeed message displays on an individual aircraft, go to the aircraft.cfg file of the aircraft in question. Find the [Reference Speeds] section and increase the max_indiacted_speed = entry to whatever you want. example: max_indicated_speed = 340 //Red line (KIAS) change it to read max_indicated_speed = 500 //Red line (KIAS) Overspeed will now not show until you reach 500 kts IAS. No flight dynamics are affected. You are only raising the barber pole overspeed warning based on the IAS instrument. This information courtesy of Jim Ville. The modifications work well on my machine - XP Operating System - and should do no harm. However, as with any freeware, you use the modified language.dlls at your own risk. Questions and/or Comments may be directed to: David "Opa" Marshall
  9. Sorry about that. Try this. https://www.flightsim.com/vbfs/fslib.php?searchid=93878566
  10. Do you by any chance have Ultimate Terrain Caribbean?
  11. Before calling my suggestion "Wrong", you might like to take a look at the seventh file entry here . https://www.flightsim.com/vbfs/fslib.php?searchid=93873329 Offered by the late, great David "OPA" Marshall. Westway did not indicate if both messages were not showing. If the "Brake" message was showing, than he could possibly have a corrupt language.dll file. If both messages were missing, than your suggested is worth looking at.
  12. The "Overspeed " (and "Brake" warnings) are set by the language.dll file in the main FSX folder. If you have access to the OEM language.dll file, copy and paste it to the main FSX folder and let it overwrite your current language.dll file. I can't say this will fix it, but it is worth a try. If you don't have access to it, send me a PM and I'll send it to you via email. Be sure to include your email address. I can't attach it here as it is not a valid file extension that Flightsim.com will accept.
  13. Have you tried selecting a different aircraft other than the 727-200? If selecting another aircraft yields the same black screen, you could try letting FSX rebuild the FSX cfg file. Go to C:\Users\your file ID name\App Data\Roaming\Microsoft\FSX\fsx cfg, Cut\Paste it to your desktop (for future reference if you need it), restart FSX and it will build you a new FSX cfg file. Select your aircraft and see if it appears on the opening screen.
  14. You can always make your own by taking a screenshot of a particular background that you desire, in jpg format and then convert it to bmp format using a paint/photo editor such as Gimp2, which I use.
  15. I think what you are referring to is the aircraft_viewer_bkgrnd.bmp file found in the Uires folder in the main FSX directory. Found this file in the library. Might be what you are looking for. fsxbgvw.zip
  16. It has been 10 years since I uploaded a repaint and I have forgotten the protocols. Is it necessary to obtain permission of an author who has created a freeware aircraft, to create a repaint for that aircraft? I ask this because I have written to the author of the aircraft in question, but have not received a reply.
  17. Ok, did what you suggested by clearing out the Flight Simulator X folder in the Documents folder so that the only entry in the folder was the saved flight data, no other data. I selected the same airport that I have been using as reference in this post and the 52 gear was now aligned with the center line. Tried another airport and the results were the same. All OK. I will now add some additional saved flights at different airports using different aircraft so that the folder will now contain multiple data entries. Will see what happens.
  18. Sure. Easily done. But my question is why this happens. OK, so I did a clean boot of FSX selecting the default C-172. See the pic. Perfectly aligned with the center line. I then selected the B-52 and lo and behold, it is also perfectly aligned. Now, on a second clean boot of FSX at a different airport, I selected the B-52 as my start up aircraft. The B-52 was perfectly aligned this time. (?) I am next going to do a reboot of my PC, then execute FSX, to see if there is stored data somewhere from FSX that is causing different results. Yes, I am retired and have WAY to much time on my hands :)
  19. Well, nothing like having to eat my own words:) I fired up FSX this morning (saved flight mode) selected the B-52 and placed it at a newly installed scenery of KCEF at runway 05. What I got can be seen in the B-52 pic. Notice the misalignment of the main gear wheels. I then selected a 727 from the aircraft menu drop down and look at it in the 727 pic. Perfectly aligned on the center line. Why the 727 and not the 52? Is it the aircraft boot order in FSX? I am going to take Napamules2 comment and advice in regards to loading the default C-172 on a clean boot of FSX. First the C-172 and then the B-52 and see what the results are. Stay tuned!
  20. How do you interpret "default" flight? If you mean the Air Creation...never. If you mean what I have selected as the opening aircraft at a particular airport...always. In my case right now, that is the Project Fokker F28 at KORH, Gate 5.
  21. Well, I was going to take a pic of what I have described and now I can't get it to replicate the condition. Tried it on the opening selection of FSX and not loading the default flight first. So I apologize for all the fuss and I guess I just have to chalk it up to a fart by FSX.
  22. LOL! That is the hard way out! No problem at all doing that. Just wondering why this aircraft is different than any other. The wheels are perfectly aligned to the fuselage but the whole aircraft is offset from the center line. Maybe the pilot needs new glasses! :)
  23. Yes, I have rudder control. It is just mystifying to me why this aircraft is not positioned directly on the centerline after selecting a runway in the menu.
×
×
  • Create New...