Adrijan Pekovic

I have managed to activate my 777 now. It seems that it works, at least for now.

I do understand that from a professional standpoint you don't want to "release" a fix that seems unofficial and bodged. However, I'm sure that most of your customers, the simmers, want to just have the realistic experience of flying and don't care that much about downloading an official update from the operations center or fixing it some other way. And, I at least certainly wouldn't mind replacing a CFG, or even tweaking one myself with the needed values if it meant having a realistic flying experience. I can confirm that the current state bothers me much more than having to tweak a CFG to fix the issue. The decision is yours obviously and I can do nothing but to accept it, but think about what's better for the customers.

It only seems to fix the nose camera. The bottom two are unaffected by the setting completely, which is odd and certainly wasn't this way before 3.3.

Completely contradictory statement by Ryan Maziarz in the support ticket I raised. I guess no fix is to be expected soon, after all.

It's been a week already.

Ticket number is 25D-1EEC7711-0402. I have definitely submitted it on June 9th with no replies as of yet. I have tinkered a bit myself with the values in aircraft.cfg, namely the [CameraDefinition.016] and [CameraDefinition.017] fields, but nothing seemed to affect it. The odd thing is that WideViewAspect=True/False in Prepar3D.cfg doesn't make a difference for those two cameras, but for the nose camera it still does.

A week has passed since I submitted the ticket to their support. How long does it usually take them to reply?

Have the same issue since updated P3D to V3.3 and WideViewAspect is set to 1.

Without wideviewaspect=true in fsx.cfg (which you must manually change, there is no other way to do so), 1.0 zoom still wouldn't be realistic. Is your wideviewaspect=true set? :smile:

The following video covers this topic extensively: To summarize, in order to get the most realistic view, zoom should be at x1.0 and wideviewaspect=true in fsx.cfg, regardless of the monitor. I personally use x0.7 as it doesn't distort the view very much (and if at all, it does it only at the edges), and it gives me a better perspective of the outside for my 1920x1080 16:9 monitor.

Pretty sure that was windshear alert from ASN, not PMDG 777 :smile: You can find almost all selcals at airframes.org, it's just that they can't know for sure it's on the registration plate in the cockpit (if I'm right). Still, in my opinion they should be included anyway on all repaints, since most of 777s have it.

That's definitely the problem. In fact, FSInn will have the problem of injecting wrong temperature above a certain altitude. Try using a third party weather engine (e.g. FSRealWX lite, it's freeware).

Do four consecutive flights count, following the real world plane in real time? http://imgur.com/a/q66VN Took me 45 hours to complete, OMDB - SBGL - SAEZ - SBGL - OMDB

Oops... accidentally posted this twice... Could a moderator delete these two posts (this and the quoted one)?

Yeah haha, Emirates will fly everything with the B77W... From a short half an hour trip to Doha to a 17 hour flight to KLAX.

Yeah haha, Emirates will fly everything with the B77W... From a short half an hour trip to Doha to a 17 hour flight to KLAX.

I've never expected such a response, to be honest!

Which ever destination of Emirates has some extreme weather at that time!

Perhaps it would've been better if I opened a support ticket directly, I just forgot that's an option . And yes, of course this is a very minute issue, I just wanted to point it out in case PMDG "missed" it. I imagine it would take less than a minute to fix it, and I assume PMDG is a company who wants to fix these kinds of issues. If not, it's okay with me. Besides, I found a few other small issues like this, but searching the forums and/or looking at the issue tracking thread, I saw that they were fixed for SP1.

When you do the fire test, the EICAS will display "FIRE TEST IN PROGRES" warning message. However, on FCOM 8.30.4, it is said that "FIRE TEST IN PROG" is what should be showing. I assume this is fixed in SP1? Cheers.

The color/placement reminds me of the FSX "NAV/GPS" button on all default aircraft :biggrin:

Just to clarify, SimBrief won't make a route for you. It can suggest some common routes but they are only from the previous guy which flew it. Usually not accurate and most airports won't have a route between them. rfinder.asalink.net/free/ This is a free route finder. It's not very good, but for beginning it's okay. And always check your route before flying it!

Tune the ATIS frequency into VHF R (by default on right radio control panel), then turn on VHF R receiver (press the circle button with the arrow). It should work with default FSX ATC and FSInn on VATSIM, not sure about Squawkbox or IVAO.

I don't think this is a good idea, since PMDG adjusted the viewpoint for the optimum reference position. Though, with FSX bugs changing the camera viewpoint, it can get off near the poles (especially while turning).

Not sure if this could cause it, but do you accidentally press the FSX fuel dump key (default assignment CTRL + SHIFT + D)?