[ Closed ] ver 2.7 beta 1,2,3 WIN/MAC 64 bit (Page 4 of 7)

Acei wrote:

Is anyone else seeing this?  I'm using 1.51 R2 with AIRAC cycle 1611.  Tells me that the data isn't loaded.  Doesn't appear to be a beta issue as I'm seeing the same on the A330.

Probably the folder is not having the correct structure

Should look like this
\X-Plane 10-64\Aircraft\Airliners\a320neoV2\NavData\
\X-Plane 10-64\Aircraft\Airliners\a320neoV2\NavData\PROC\

Again a huge thanks JAR !

I have some questions :

-how to set the new "ground set" ? Is it something to download ?
-perhaps stupid question but how to change views quickly (as in the differents demo from BSS on you tube : for example right view on the right passagenger and then very quicly in cockpit again)
-in upcoming betas would it be please possible to implemente : the T.O inhibit functions, the displays of the speed and alt constraints on the ND and at start when aircraft is shut down to have the orange cross on the display like on the A330

thanks a lot for all your great work

log.txt, bbox.txt and MacOS crash report attached for one of my many CTDs when approaching airport.

Nice Update Eugeny and mouse control is great. Thank you very much for that!!

Some first observations:

• I like using the mouse wheel but X-Plane is still zooming, when I miss a switch/ knob. I tried the plugin xscrollwheel which helped last year with the FF A350. But when I disable the mouse wheel with that plugin, I cannot control the switches/ knobs in the A320 anymore

• Had a bug yesterday. Made a freestyle flight in very low altitude and the GPSW started to say one of the warnings listed below and GPSW warnings were running in an endless loop. It did not stop even if I started to climb to FL100..

These warnings came without stopping:

• Terrain, Terrain!

• Too low, terrain!

• Sink rate!

• Don't sink!

• Too low gear!

• Glide slope!

• Pull up!

• Too low flaps!

It did not stop until I stopped the flight.

Cheers,
joomie

Better to use following common folder for all aircrafts:
X-Plane 10\Custom Data\GNS430\navdata

hdw wrote:

I've flown this  2.7 beta today (windows 10) and found following issues:
1. All displays (including landing gear green lights, brake lights) grow dark as the daylight grows dark. Setting daytime to e.g. midnight, then displays are dark, even when the reostats are set to full bright. Flying in clouds with strobes on, the clouds flash and accordingly the display lights flash.

On point 1 - I've had that issue in the past and discovered it was a script included with Real Terra Haze that was affecting my lighting. This wasn't unique to the JAR. Are you using RTH? If so, remove the "dazzle.lua" script from your FlyWithLUA scripts folder. You will still be able to use RTH.

Is anyone else seeing this?  I'm using 1.51 R2 with AIRAC cycle 1611.  Tells me that the data isn't loaded.  Doesn't appear to be a beta issue as I'm seeing the same on the A330.

I tried this beta version. Few things noticed:

- There is a clickspot to turn on/off screen reflections for PFD, ND, ECAM et cetera. a) it does not save your preference after closing X-Plane, b) this reflection effect is not applied on the MCDU.
- The green effect on the windshield is a bit too odd and too much indeed. However, in the JARDesign Facebook group I posted some pictures about what is possible to make is very very great. X-Craft did it very wonderful. But on the other hand, X-Plane 11 will give this reflection feature as well.
- The cockpit and cabin windows have a too grey tint. As a result: it looks like it is always a foggy day.
- The spoilers after touch-down deploy too fast/too instant. They have to deploy a bit more gradually/smooth.
- There is no intertia involded in the tiller. This inertia is involded in the A330 which is super, but the A320 is missing this. As a result, you are able to perform smooth taxi operations with the A330 and to counter-steer a bit. With the A320, it results to weird and harsh movements.
- After a long period, I also tried the A330 this weekend. The FBW of the A330 is much better than the A320. So, I really hope the FBW of the A330 can be used for the A320.
- Very shortly after airborne, the A320 tends to make a little nose-down effect. This same applies shortly before flaring.
- When I disconnect the autopilot, sometimes the aircraft is going crazy and makes an abrupt nose-up movement.
- The auto throttle system is going crazy when there is (little) turbulence. It is too responsive to every little speed difference due to the turbulence.
- When reaching TOC, the power management is a bit odd. When reaching TOC, thrust is going to idle -> reaching TOC -> applying thrust. This is not correct. When reaching TOC, the thrust just reduces a little and the pitch angle just decreases gradually.
- Same when changing the speed in the FCU. When you change the speed in the FCU, the FADEC makes too abrupt changes. For example: you fly speed 290, want to reduce to 250, hence you dial in 250 and the thrust is going to idle almost instantly and when reaching 250 is applying thrust like we are going to take-off in the air.

This are some points. I hope they make sense and can be taken into account to future update(s)

domined39aniello wrote:

Hi Sir Romanov can you put the light in the cabin passenger ,even for those who can't to use a HDR?
Thanks for your work

Sure, 3D light is expensive for videocard calculation, but "LIT"-lights are expensive for videocard memory. Since we get 3D light we use this as preferable way and follow "no LIT-textures" trend.