Relayer91

Ah superb thank you for that!

So, I'm getting to grips with making new liveries - currently mostly GA - and one of the problems that seems to be causing me a real headache is getting the angles correct when a curved shape (i.e like you see here - https://murmerair.com/wp-content/gallery/paint-schemes/pilatus-pc12-scheme-2.jpg ) runs across multiple parts of a texture sheet, or even an entirely different sheet. I can line up the two shapes (with a hefty dose of trial - error - shift it down by 3px etc) but whenever I try to make a new shape to continue a smooth bezier curve on another part of the sheet, I just can't quite seem to get the angles 'right'. Is there some tip / trick to getting this right, other than just 'git gud'? It probably isn't helping that I'm using Carenado / Alabeo aircraft just now, as I've gathered their unwraps are pretty horrid to work with - but people like Ron seem to manage absolutely fine with them.

So, as something of a surprise, PMDG just dropped their updated NGXu base package, and while we're all off scurrying to try it out, I'm sure it won't be long before we're itching to have our virtual FO along for the trip again. I know it probably won't be just a straight port-over from the FS2Crew Reboot, and it'll probably take a while, but would I be correct in saying that most likely we'll see an FS2Crew update for this at some point?

Do you have *both* VHF Nav control panels set to the ILS frequency, and inbound runway course set on both course windows? The autoland system will not engage unless both nav radios and courses are set identically.

I suspect it isn't a bug, as the following paragraph appears in the Continental Airlines MD80 FCOM - 'It is recommended that Indicated Airspeed (IAS) be used as the cruise speed reference. Mach number is a function of OAT and variations thereof cause excessive and unnecessary throttle “hunting.”'

I'm having issues with Vox 6.51 and P3D V2.5 with the first hotfix applied - it seems that the FO option doesn't work properly. I'm wondering if anyone else has run into this, and whether it's an issue with Vox, or possibly some kind of FSUIPC issue. The problem is, it seems the FO cannot interact with the aircraft, change radios etc. And when 'he' goes to make a radio call, it gets stuck on 'First Officer is operating radio', causing all other radio traffic to go a bit funny as well.

I am, yes. Not had any problems with it before, I'm currently using Steve's DX10 Fixer. I'll try updating that and see if that's possibly causing the problem.

As an update - I bought and installed the -300ER package last night, and the same problem is affecting it. Maybe FS2Crew related, as that's about the only thing I've changed? Although quite why that would have anything to do with the alpha channel on the textures is a bit beyond me.

I can also reproduce this - I've been wondering what's caused it for a few weeks now.