Jump to content

f16jockey_2

Registered Users
  • Posts

    1,429
  • Joined

  • Days Won

    1

Everything posted by f16jockey_2

  1. Second option, but overwrite sound.cfg with the downloaded one. Your first option would destroy the DC3-sounds. Another option: in the JBK folder, create a folder sound.Barreto. Copy the downloaded sound.cfg and sound files in that folder. In aircraft.cfg, for each [fltsim.x] section, change sound= to sound=Barreto. This also gives you the option to easily revert to the old sound. Wim
  2. As you stated my suggestion (amongst others) to "Verify Files" in the other thread didn't lead to any results, a clean reinstall is the only option I see. Wim
  3. Not such a good idea... Looks like one model has nav lights as part of it, while the other model hasn't. Create a separate aircraft folder (with a separate aircraft.cfg) for the PA 320 model with the duplicates. In that folder, removing the nav lights from aircraft.cfg should do the trick. Wim
  4. Uninstall every single ORBX product you have through ORBX Central. After that, check manually if any traces remain, and delete those as well. Reinstall everything, starting with Global, then Vector, then the OpenLC’s. Wim
  5. ORBX Vector User Guide page 10 Wim
  6. At the end of the thread, it’s revealed that the initial error was caused by REX Weather Engine, so I seriously question the speculations and semi-thruths stated at the beginning of that thread. Wim
  7. Stock FSX doesn't use .NET Framework. Must be an addon. Wim
  8. I think the bridges are part of the VECTOR package, not sure though. Run Orbx Central, and do a "Verify files" on the package. Wim
  9. You mean they have a blackish texture applied, or rather black 'cos of a missing texture? Anyway, this is how the bridges appear on my install (same Orbx products as you). If this is what you call black, then so be it... Wim
  10. A waste of time? Depends on the gauge available IMO. On a simple VOR-indicator it's useless indeed. On a HSI-style gauge I set the ILS-course for general awareness. But as said, this has no influence on the AP behaviour. Wim
  11. Be aware! While in FSX stock airports (and many freeware addons) the physical numbers (as painted on the ground) simply can be changed through ADE, it's mostly not the case with payware airports. Payware airports use textured ground polygons for the visual appearance of the runways. One has to edit textures to change that. It's very well possible that your modified BGL is active, so ATC will call "06" in stead of "05R". Dunno if you've tried that. But the appearance in the sim will still be "05R" until you modify the textures. BTW: stay away from it if not an experienced repainter. And make backups, lots of backups... OTOH maybe there's an update in the pipeline at PacSim? Wim
  12. The resulting BGL must be placed in an active scenery folder. When starting FSX, you should see a pop-up saying FSX is rebuilding it's scenery database. Wim
  13. You're absolutely right. This package is a mess. When the FS9-package was released, they used certain model names (including B--W2). When the FSX package appears, the model names have changed. No trace of Model.B--W2 anymore. Model.B--W2 is now simply called model.W2 (I think...). Confusing at least. What follows is hilarious: when releasing updates (on FaceBook) for the FSX version, he changed to using the FS9-names again. So magically model.B--W2 appears in the updates, while it wasn't there in the original release. Applying the updates must be a real puzzle. Good thing you got it solved, but until I really NEED a 737-700, I'll pass on this one. Wim
  14. If you didn't make a backup of your complete FSX installation, even after your MD-83 mishap, I can only agree. Wim
  15. Search for a very basic schematics of a QWERTY layout. Print it out and pin it on the wall somewhere (preferably where you can see it ;)). If some key doesn't work as it's supposed to, search for the location on the above picture and type the corresponding location on your AZERTY keyboard. This has worked for me ever since the nineties, for simming and for many, many other games. I'm from the Flemish part of Belgium, so we use AZERTY as well. After a while, you won't need the picture anymore. But I confess, I still have one on the wall. Wim
  16. I'd NEVER board an airline called "Air Saint Peter". Who knows where it may get you. There's a repaint at AVSIM for the payware Carenado btw. Wim
  17. Yes. Make adjustments to PitchPanRate and HeadingPanRate. Wim
  18. Both lines with = Ordinal to = Swivel? YES. Only then you'll be able to pan around. Both lines with Return in it. Depends on what you want. If = True, then the view will return to centered when you let the hat-switch go. My idea would be to just try both options, and see what you like most. It won't break anything. Remember to make a backup. In fact you already did by posting yr current content in this thread :cool:. Wim
  19. In cameras.cfg change the lines in red. This file is located in C:\Users\\AppData\Roaming\Microsoft\FSX (the same location as the active FSX.CFG) [CameraDefinition.001] Title = "Cockpit" Guid = {B1386D92-4782-4682-A137-738E25D1BAB5} Description = This is the description of the cockpit view Origin = Cockpit ShowPanel = Yes [color=#ff0000]SnapPbhAdjust = Swivel[/color] SnapPbhReturn = No [color=#ff0000]PanPbhAdjust = Swivel[/color] PanPbhReturn = No Track = None ShowAxis = Frontonly AllowZoom = Yes InitialZoom = 1.00 SmoothZoomTime = 2.00 ShowWeather = Yes XyzAdjust = Yes ShowLensFlare=No Category = Cockpit PitchPanRate = 10.0 HeadingPanRate = 15.0 Panacceleratortime = 0.0 HotKeySelect = 2 Wim [EDIT]Noticed too late you're using FSX-SE. File location may vary, but I think it's the same?
  20. I don't have the aircraft, but that sounds like the Decision Height setting. That's the height AGL were you need to actually SEE the runway for being allowed to land it. It's different for every airport, runway, the approach you take for that runway, even the type of aircraft (it's intstruments) you're flying. You need to read charts for that. In general 200-250 ft is a reasonable setting. Wim
  21. Select "Save as Extended Bitmap", then select the desired option from the dropdown. Wim
  22. C:\Users\\AppData\Roaming\Microsoft\FSX\GrantedRewards.BIN Delete or rename it, or backup to another location. Wim
  23. The large majority of WoAI are FS9 models, so DDS won’t stick on them. In case of FSX models, don’t forget to flip the image vertically. Wim
  24. Why don't you just try? It won't break a thing when making proper backups. But I guess you won't us to try that first? :cool: I don't have any of the A2A Mustangs btw... Wim
×
×
  • Create New...