Wolf0

I've just noticed that on AS16 you've implemented this suggestion. Thank you for listening. :-)

Hello. I have the same setup. Aerosoft Airbus with ch throttle. I have everything working using fsuipc and the tutorial on this thread. You'll need the lua files refered. I'm not sure if the link still works. Let me know if you need any further help. http://forum.aerosoft.com/index.php?/topic/60794-ch-throttle-quadrant-idle-thrust-woes/ Pedro

Just to add my findings to this topic: updated from 3.2 to 3.3.5 (hotfix) via the client upgrade method. I updated the sim hoping to get rid of a problem that I was experiencing with some RF Scenery Building airports (LICC, LICR, LIRQ, LFKB, LFKJ, LSGG and UMKK). These airports had runway textures that were disappearing when the viewpoint was in a certain angle. We had a topic here on avsim with a user showing the exact same issues only with a custom made scenery: www.avsim.com/topic/488783-scenery-disappearing-under-certain-angles-p3dv32/ youtu.be/GIizdVTdKA0 This was related to a z-bias bug that was preventing the correct order of the textures to be displayed on 3.2. As stated on the new P3Dv3.3 features list: «Fixed custom z bias scenery flickering issues including runways and runway markings» With 3.3 all these issues are gone, and these airports are now 100% operational again. In conclusion: for me it's a good update. Performance wise it looks the same as 3.2 and it's good to think that we feared that we'd loose backwards compatibility on some (FS2K2 SDK) sceneries, only to find that we gained more flexibility. At least for now!

Wow! I'm glad that you guys liked the suggestion. I'll be looking forward for this new feature. Pedro

Hello. I have a question/request about a ASN characteristic. Currently, when an airport has a METAR without wind information caused by the anemometer being out of service (represented by the field //////KT where the wind direction and speed used to be), ASN interprets that field as zero wind. This can be verified at Lajes field in the Azores (LPLA). The anemometer is inop and the surface wind injected by ASN is 0KT. Current METAR at the time of posting: 016/05/05 09:00 LPLA 050900Z /////KT 9999 FEW015 15/11 Q1023 While this may be a benign solution to the problem of dealing with those rare situations when an airport loses the wind information, it could be improved by interpolating the wind of the nearby airfields to reach a value for the airport without wind information, as the software does for dozens of places without oficial METARs. I'm aware that this situation is rare, and probably not worth the investment of coding additional lines to be dealt with. But nevertheless it would be a nice feature to have. Best regards, Pedro

Hello. Some time ago I reported a problem with the Aerosoft Airbus FPA display not updating correctly on the VRInsight FCU hardware using the latest builds of LINDA. Today I was finally able to track down the problem and solve it. Here's the solution. Open the file «common.lua» on (...)\Modules\linda\system. Search the file for the function «DspFPA». On my file (LINDA v2.6.7) it appears on line 3902 with this text: «function DspFPA (i)». This is the function that updates the FPA value on the VRInsight hardware display. Line 3906 of the default file reads: «if DSP_VVS_PREV ~= strVal then». This is the wrong variable call. Replace the text with: «if DSP_HDG_PREV ~= strVal then». Backup the original file, save the changes, reload LINDA and start the simulator. Enjoy the decimals on the flight path angle!

+1

Ok, it's time for an update regarding the taxiway bridges issue. I've received an email from Taxi2Gate with an hotfix for the problem and just tested it with good results. As from now, the airport has no "major" issue that prevents it's use. A global update is also scheduled, correcting other bugs. Personally, I think this is good customer service. A major problem slipped testing but showed on some user systems. An hotfix was produced, tested and shipped to the costumers in 24h time. That's pretty good in my opinion. Now it's time to spend some hours enjoying this quality scenery. We tend to only point the faults, but the truth is that T2G built an visually enjoyable, accurate, VAS and FPS friendly version of one of the major European airports. If only we could have one of these for every major city out there... Good job, Taxi2Gate! Now let's see Paris!

Hello. I confirm both issues refered on the previous posts. 1) Approaching the airport at night, the grass appears way too bright. Like carlito77 said, it glows. The posted picture is a good example. 2) Altough I didn't try 《every》 bridge, I couldn't cross the "SB" bridge. The aircraft taxied form "S" to the bridge, and there was an obvious ground height difference. Like a step. And there was another exiting the brige, inbound the terminal, resulting in a crash. This was at a rather slow taxi speed on the Aerosoft Airbus, P3DV3 and no previous mesh issues. Looking for a fix.

I use it to keep the clock sync'd with UTC time. Plus it corrects several timezone bugs present since FS2004 (FS2000?)...

Hello. I use FsRealTime and I can confirm that (in my setup) it works flawlessly in Prepar3d v3. The software is frequently updated, usually right after a Fsuipc iteration. I can only praise FsRealTime. It's been around for a long time and I never had a problem with it.

Thank you :smile:

Hello. If possible it would be nice to see what is happening with LINDA when using the Aerosoft Airbus module and flying in TRK/FPA mode. In my setup the FPA window on the VRInsight FCU only shows every ~1º change, while the aircraft shows every 0.1º (that matches the lowest possible selectable number on the panel). I think it is some kind of window refresh problem with LINDA that hasn't been spotted yet. All the other rotary switches work as designed. Only the FPA mode presents this glitch.

Hello. I'm having a problem using the latest builds of LINDA and the Aerosoft Airbus module (4.3v2). I own a VRInsight MCP Combo II Airbus FCU which works great with LINDA, apart from the FPA (Flight Path Angle) function. When switching to FPA mode, the Track window works great, just like the heading mode, but the Angle mode doesn't. On the VRInsight panel the angle value (the display where the vertical speed used to be) has a "lag" when rotating the dial. On the simulator the FCU shows every 0,1º change (i.e., FPA 2,2; 2,3; 2,4; etc.), but on the VRInsight panel the numbers don't change with the dial. Apparently only when the change is bigger than 1º (10x0,1º steps) does the VRInsight display receive an update and shows the correct value that the Aerosoft FCU is showing. This happens both with the Airbus 1.21d and the new 1.3 (SP3) released today. I should add that everything used to work great on the early releases of the Airbus module regarding this TRK/FPA subject on my setup. In fact I'm surprised no one has yet noticed this... maybe because TRK/FPA mode isn't a very used mode... Anyway, some feedback would be great. Wonderful work with LINDA and the Aerosoft module, btw. Really useful. Thanks for the hard work! Pedro