horace

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:

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?

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

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)

Ok guys. All is fine! I had some very weird settings for the spoilers axis.

Cool! Thanks Bryan!

Mahlzeit Any specific setup in your case? Nullzones or anything like that?

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.

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?

Hi Bryan, yeah, I'm using SOP3. But in my case I can't stop him using it ^^

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

Hi, USE VSD (FO’S SIDE) is set to NO. FO uses VSD nevertheless. Cheers, Hendrik

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

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

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

Hi guys, I'm trying to figure out a solution for the problem as seen in the shots below. As you can see close to the horizon the haze or fog layer is cut off and somewhat tiled. I already did my best to break down the problem as much as I can and it does only occur when running in DX10 mode. The problem is especially noticeable in combination with ASN, which I run with default settings (except for cloud draw distance and visibility limits). ASN has an option called "auto adjust upper visibility" and it's activated. With this option disabled the problem seems to have vanished due to raising the visibility limit but of course the look and feel is way more unrealistic without. The next situation where the problem is very present is when flying through fog. I grabbed a screenshot (the second one below) from a thread in the HiFi forum, where a user is reporting that issue... but without specifying, if he runs in DX10 mode or not. A tool suspected to be the cause in that thread is Shade which I'm using as well. But I tested without shade (restored default FSX textures) - the outcome was the same. So I'm stuck here at the moment and requesting for help What else can I provide... ASN is configured with a maximum upper visibility of 115 and maximum cloud draw distance of 140. I fiddled around with the settings and also found out the the problem is present with visibility limits below approx. 70 miles. Anything above will be fine. I'm using exactly the Nvidia Inspector settings as per this thread: http://forum.avsim.net/topic/426219-proper-nvidia-inspector-settings-wiht-dx10-fixer/ Have anyone of you seen the problem as well? Know how to fix? Thanks in advance! Best regards, Hendrik Horeis

Guys, give VC a try! It's definitely worth it! Trust me and all the others out there pointing the same. To be honest, I also was kind of suspicious that days around release of the NGX. BUT! You will start getting used to it very soon and you are not gonna miss the despicable 2D version at all. It's the ultimate truth. If you are worrying about your PC Setup... as harsh as it may sound... go get a new one, it's time. You can not expect a bleeding edge development like the 777 to run on an outdated setup. Posted this as it gets me very annoying to read those posts on the one side and understanding those complaints on the other side as I went through the same struggle a few years ago :-) Cheers Hendrik

For sure!

To be honest with you... I'm not familiar with the static_pitch and static_cg_height parameters and the way they might affect flight performance and could be the cause for odd behaviour. But well, ok. I'll stick with it until anyone yells at us ^^

Good Morning As I prefer to use AES on covered airports and GSX for the rest, I would like to ask, if it is safe to use the repair for pushback function within AES which will slightly modify the aircraft.cfg: //AES Orgvalue:static_pitch=-0.465 static_pitch=-.79 //AES Orgvalue:static_cg_height=13.060 static_cg_height=13.22 Have not discovered any anomalies so far but I'm quiet concerned about 3rd party modification of well tested parameters. Without the repair to push thing the aircraft would constantly jump during pushback. Any advice from the dev team or AES users? Thanks in advance, Hendrik Horeis

>Why not convert the textures yourself?>Just open them with DXTBMP and save them as DXT3.If it's as simple as that I should give it a try. thanks :)

Hi,I guess Marek was talking about the Pax Version. Well if someone could tell me if there is a SIA DXT3 livery on avsim, everythings gonna be fine ;)

>1) I am realy realy dissapointed about PMDG withg regard to>the SIA 744 model.All the airlines came out and this one is>still missing for download. I dont want to use any other>download from the AVSIm file library.So when is it finall>ycoming out.Can't help you with that ... I would also be pleased if PMDG would release one if time allows.>2) I was flying EDDF to KMIA using the Route Finder way>points. The route was giving me NATS like 54N030W and 54N020W.>I couldnt put them in the FMC. They dont exist. As i was>flying this route (without the NATS) its looks like that they>dont even exist on the plan. Please adviseYou have to enter them in this manner:5430N5420N...and so on.Here are some other examples grepped from another thread somewhere in this forum:N latitude/W longitudeN52 00/W075 00 = 5275NN50 00/W040 00 = 5040NN07 00/W008 00 = 0708NN75 00/W170 00 = 75N70N07 00/W120 00 = 07N20N latitude/E longitudeN50 00/E020 00 = 5020EN75 00/E050 00 = 7550EN06 00/E008 00 = 0608EN75 00/E150 00 = 75E50N06 00/E110 00 = 06E10S latitude/W longitudeS52 00/W075 00 = 5275WS50 00/W040 00 = 5040WS07 00/W008 00 = 0708WS75 00/W170 00 = 75W70S07 00/W120 00 = 07W20S latitude/E longitudeS50 00/E020 00 = 5020SS75 00/E050 00 = 7550SS06 00/E008 00 = 0608SS75 00/E150 00 = 75S50S06 00/E110 00 = 06S10

Hi,you should find them here I hope: https://164.214.2.62/products/digitalaero/index.cfm

Nice to hear from a technician, very interesting! :)I also didn't expect the 744 to have only one A/T motor, that surprises me. However, for a workaround I'll simply switch the A/T off if I need one at idle (e.g. an inflight start) - that's not a too big problem at all.Thanks, it helps and hurts in the same way :(