klisura

Hi Dave, in single cockpit everything is ok. I use differential brakes bound to toe pedal. I found other people on Facebook with the same issue

Dave, what's the difference between my setup and the one recommended (null zone setting apart)? And one question is still unanswered: why my setting works with A320 (and every other airplane) and not with A330... Unfortunately I can't do any further attempts because my mate is in a terrible moment (he lost his mum). I'll try in next days, no hurry. There are most important things to care about now... Thank you for your attention and support Bye Kli

Here's my calibration settings. My CFD mate tried to delete brakes bindings (he doesn't use pedals, just brakes on a joystick button) but without success. We have red "Brakes" signal steady and it prevents to release parking brakes

I use saitek pedals and I use toes for differential brakes. I've calibrated it and set a null zone too. I don't understand why it works in A320 and I have issue in A330. Tomorrow I can check it with you if you have time, now unfortunately I can't

So how do you explain that the issue is only on A330 while on 320 everything is ok?

Same problem here. Brakes advice is steady red on left bottom corner and no way to set parking brakes

Well it's what is written on mcdu CFD Page. I'm glad it's going to beta

I hope that A320/330 promised features as new ND system, pop up displays and a final version of CFD (it's in "very alpha stage" yet) will be accomplished in P3d version and not abandoned with the excuse of the upcoming new MSFS

When can we expect CFD in final release? Is it still alpha?

Alitalia https://www.flickr.com/photos/38998307@N05/26290726574

Robert it's the scenario! That's why if you generate a new cfg p3d doesn't crash, because it starts with F22 default aircraft. While if you save a scenario with A320 then if you launch A330 you have a CTD. So p3d has to start with a default aircraft

Thank you Dave, I appreciate your kindess. Regenerating p3d.cfg has partially solved my issue. I know it's not my system because my friend @waltervizzi experienced the same and so others here. I think not everybody has updated the 320 and who did maybe didn't try to launch the 330. Anyway best luck to everyone and thank you again

I assume that after a320 update to v.1.3.0 the A330 doesn't work anymore and make p3d crashing in the exact moment I try to load the A330 and I'm not the only one. Something like "we are sorry, we take a look at the issue" would be appreciated instead of "we have billions of user without issue"

Sorry, as always, it's my (our) fault. Thank you for assistance

Bill, delete p3d.cfg file (remember to backup or take a note of every single p3d setting, export joystick settings) then run p3d again in order to let it generate a new .cfg file That solves the issue