Jump to content


  • Posts

  • Joined

  • Last visited

About cconesa

Contact Methods

  • MSN
  • ICQ

cconesa's Achievements


Newbie (1/14)



  1. Hans, I can confirm that I noticed an improvement with the new .DLL (P3DV5.1). Will do some further testing to make sure improvement is across the board and in with various sceneries and report. Regards, Christian C./ Specs: i9-9900K CPU @ 3.60GHz, 32GB RAM, NVidia RTX2080Ti
  2. I further report that changing the start up situation does have a small effect to the FPS but stutters and highly volatile FPS count remain. I cannot remember this being an issue on v2.2, in fact, I remember the CRJ being quite benign on the FPS front. Also, the reverse thrust does not really have much of an impact at slowing down the aircraft. Regards, Christian C./
  3. Hello Hans, I have just started from cold and dark and my frame rates are not running smoothly. I am getting an average of 16-25 fps when I would normally run 30 fps without a problem (they are capped at 30 fps). Didn't have this issue before. I will try in a while with a turnaround state to see what happens then. Regards, Christian C./
  4. Thank you for your reply and forgive me for asking, but, why the "no promise" comment?. This is a bug, easy to spot/replicate and just needs a little bit of an effort to resolve it. Has any further development of the A330 stopped?. Regards,
  5. Hello, This is outstanding and remains unresolved after several months. I don't think it is to do with the tracking system, it has to do with the gauge and font sizes/location. Will be grateful if you can look into it and fix it. Regards,
  6. Hello, Two patches have been released since pointing out this error and this matter remains unsolved. Do we have a ETA for the fix?. Regards,
  7. Thank you. Does that mean the the solution is to change the gauges in [window06] and [window07] to a 508,508 size?. Edit1: Just tried it and doesn't work, the solution is elsewhere... Edit2: It amazes me that no one has noticed this issue before...
  8. Can anyone help with this, please???
  9. Hello masterhawk, did you have a chance to check the ECAMD2D.dll file for the inconsistency in the pop-up gauge?.
  10. I can confirm that the same behavior is present in v1.0.2.0.
  11. Yes, a slight widening of the ECAMU solves the problem but not the ECAML, it is something to do with the pop-up gauge ratios or the gauge itself (more likely). I thought maybe chase plane had something to do with it and installed the A330 fresh (including latest patches) with no chase plane but the problem remains. These are the panel setting for the ECAMU pop-up from the original fresh installation: [Window07] Background_color=0,0,0 size_mm=213,302 windowsize_ratio=1.0 position=8 visible=0 sizeable=1 ident=10025 gauge00=../../Aerosoft A330 Professional Base/Panel_Fallback/Airbus_ECAMD2D!AB_ECAML, 0,0,213,302 and this is from [Vcockpit03] : gauge21=../../Aerosoft A330 Professional Base/Panel_Fallback/AB_Systems!AB_ECAM_EWD1,0,0,1,1 gauge22=../../Aerosoft A330 Professional Base/Panel_Fallback/AB_Systems!AB_ECAM_EWD2,0,0,1,1 gauge23=../../Aerosoft A330 Professional Base/Panel_Fallback/AB_Systems!AB_ECAM_Memos,0,0,1,1 It would appear that the pop up gauge (ECAMD2D!AB_ECAML) is different to the actual virtual panel (AB_ECAM_EWD2 or _EWD1?). Is that correct? Edit By the way, the ECAML error only happens with the CRUISE page and not with the other pages. It would seems it is related to the XML for the pop-up gauge?.
  12. I'm running 4K, 3840x2160. Funny things is that ECAML works fine for other status screens (pages), it is just the "cruise" mode that has the error. The ECAMU is just the one page with the misalignment on the EPR numbers.
  • Create New...