Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

horace

Members
  • Joined

  • Last visited

  1. Although REX isn't the root of all evil. Both REX and ASN are just trying to work around some significant changes that allegedly have been made by LM for the current 3.2 release of P3D. No official statement yet by LM that I am aware of but I'm pretty sure things will improve with the next release. For now, I fiddled around that by setting cloud size to the default 0.50 within REX and instead of using 4xSGSS with Inspector I'm using 4x DSR and not using Inspector at all. Keeps my GPU (GTX970) within limits even in cloudy situations. Volumetric fog is on, Multiple visibility layers is on in ASN, 85nm max upper vis. 85nm mincloud draw distance, 95nm max. This seems to work fine, at least for me. There are some glitches with the upper visibility though.. But I decided to just fly instead of tweaking around now :smile:
  2. Hey, yeah, had the same thought and tried the 361.91 yesterday with same outcome. I think there have been enough reports and I'm pretty sure someone of the HiFi team will soon acknowlege, that they are working on that issue. There is a thread in the HiFi forums and in the Avsim HiFi forum as well and as far as I remember, some of you out of this thread also filed a support ticket. Looking forward to some news. To revert is not really an option as there was that sky haze problem, right?
  3. After spending some time, I found out that both fx_1.bmp and fx_2.bmp in the main effects/texture folder somehow were corrupted. I don't know which addon actually is responsible for that, but I just restored both files from a backup and everything is just fine
  4. Hi, I would also be very interested in what's going on here. Purchased 737 and 777 packages yesterday... this is what looks like a serious engine problem, but it's not https://drive.google.com/file/d/0B7atr7ZoqbqYMkFWeFNwRjhjVW8/view Special effects detail is set to high. Running P3D v3.1 on Windows 10 64 Bit. Addons: Rex with Soft Clouds (Sky, Cumulus) Fex (Cirrus)
  5. Ok guys. All is fine! I had some very weird settings for the spoilers axis.
  6. Mahlzeit Any specific setup in your case? Nullzones or anything like that?
  7. Ah yes. Let me try to set up a nullzone to make sure it's position is definitely 0. I will also try to disarm it via the key command to see how things work out. Thanks so far. I will report back here.
  8. Hey Bryan, below 20 knots you say huh?... that could have been the problem in my case but I'm not sure right now. Will do some tests this evening! That's a good point. And yes, I do have a lever of my Saitek throttle quadrant assigned as spoiler axis through FSUIPC. Could that be a problem?
  9. Hi Bryan, yeah, I'm using SOP3. But in my case I can't stop him using it ^^
  10. SPOILER TRIGGERS A.LDG FLOW is set to YES but FO does not start his flow after bringing spoilers in the down detent position. I have to bring up thrust first and continue taxi for a while before FO buddy wakes up. Cheers, Hendrik
  11. Hi, USE VSD (FO’S SIDE) is set to NO. FO uses VSD nevertheless. Cheers, Hendrik
  12. EDIT: oh disregard, I just read the last 4 answers. Thanks guys for clearing that up. We're all counting on you :blink: Well, that sounds really odd... literally ^_^ I will also ask my contact again. It hasn't been too long ago he told me so (half a year ago) but there might be the chance something has changed since then. Could be more likely that this is the case, as you transcribed the SOPs according to your consultant more recently... or something went terribly wrong in terms of interpretation of our contacts Incredible level of detail by the way! #firstworldproblems Hendrik
  13. Hi there, first: Awesome work! Reboot takes NGX immersion to a even higher level. I noticed one tiny thing. As part of the after landing items the FO should set the MCP altitude to missed approach altitude + 100. That's what I understood from a real world pilot working for that particular airline. I assumed that's also the reason why you have to put the missed approach altitude in the FS2Crew arrival page. What the FO does at the moment, is to set 3100 on the MCP. At least for the last three flights I did. Can somebody confirm that? Hendrik
  14. I feel free to do a cross posting here :rolleyes: http://www.hifitechinc.com/forums/showthread.php?2203-Low-visibility-with-artifacts-in-the-horizon Greets, Hendrik Horeis

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.