Jump to content

Acerazus

Members
  • Content Count

    31
  • Donations

    $0.00 
  • Joined

  • Last visited

Posts posted by Acerazus


  1.  

    4 hours ago, Acerazus said:

    @Kaiii3 is still looking into it.

    Okay, here's an update:

    The addon.xml file was corrupted because I saw the prompt when loading AILRP for the first time to remove the effects section in the addon.xml because I am still using FLAI models. Ended up reinstalling AILRP. After reinstalling, AIM successfully managed to verify files. This solved the missing nav lights on my 737s. However, it has still not fixed the issue of being able to adjust the nav lights on the A320 family. I disabled dynamic light intensity and so there should be no nav lights reflections off the ground. After applying that setting and restarting P3D, it seems that no changes were made.


  2. 7 hours ago, Kaiii3 said:

    Hey,

    here some questions I need to know to get an basic understanding of what is might going on:

    1)P3Dv4 or v5?

    2) After Running OCI "Verify Setup", AILRP Apply Effects and a restart of AIM are the files in <OCI>\Effects called "*.ailrp"?

    3) Does this happen on ALL A32X Models or just a few?

     

     

    Hi,

    1) P3D v4.5

    2) There is no .ailrp file in the Effects folder. I've noticed that since updating AIM to 1.0.2 I always get a message asking me to verify files every time I load the program. Also, when clicking on "Verify Setup" it runs something but then the entire AIM closes, is that normal?

    3) So far it's affecting all A32X models I'm seeing. I forgot to mention that they don't have the while nav light on the rear for some reason.


  3. Thanks for your reply. I'm currently in expert mode and this is what I see with default settings for the A320 family: https://prnt.sc/12d8gvq

    I created a group which focused on the A320 family. I've adjusted the settings for the nav and strobe lights however no changes were made even though I applied the settings.

    I'm guessing you're right that I'm having some effect conflict with AIG OCI? All A320 family models are from FAIB.


  4. Hello,

    I've recently purchased the AI Lights Reborn pro edition. I'm still trying to get used to the configurator so apologies if the solution to my problem was just a missing step.

    I've noticed that the AIG A320's nav lights are very bright to the point they illuminate on the ground. I've also noticed that the B737s have no nav lights on at all. Apart from that, all the other planes seem to use the light presets that I applied via the configurator. I have clicked on "Reset SimObjects" and "Verify Setup" in the OCI settings, with no luck.

    Lastly, as I fly on vatsim most of the time, is there an option to override Vpilot lighting behaviour on other aircraft? I notice a lot where pilots seem to leave their strobes on when at stand, especially those flying in the A320 family. I believe that pilots flying the Airbus have left the strobes in the AUTO position when on stand. Here, I'm guessing that Vpilot is assuming that AUTO=ON and so the strobe lights illuminate, when in reality they haven't.

    Thanks.


  5. Hello,

    I'm enjoying the FS2Crew package for the FSLabs. I have a few queries.

    I like flying in the FO seat. However I've noticed that as Pilot Flying, the PM seems to use my MCDU during the climb phase. Is there a way to solve this so that he uses his own MCDU on the Captain's side?

    I've now noticed that the PM doesn't turn on the strobes when I call the below the line checklist before lining up. As well, he doesn't turn on the Landing lights when I say takeoff like he usually does.

     

    Many thanks,


  6. On 11/2/2019 at 4:47 PM, gregda said:

    I'm having the same issue.  I uninstalled CP and re-installed and still the same.  I won't launch at all - either manually or when P3D starts.

    I found the solution. 

    I ended up deleting the exe.xml file in %appdata%\Roaming\Lockheed Martin\Prepar3D v4 and chaseplane started working again when I re-launched P3D.


  7. Hello,

    I completely have no idea what I did, but one day, I start up P3D and Chaseplane fails to auto-lanuch beside it. I have checked the settings and auto-launch for the correct sim is checked. I even reinstalled chaseplane but with no success.

    Has anyone else had this issue and maybe know the solution to this?

    Many thanks,

    Acer


  8. Hello,

    After downloading the FSReborn Lights, I've really enjoyed the improved realism with the brightness of lights and patterns on aircraft. I am using FLAI as model matching for vatsim. I noticed however that a lot of aircraft will be parked up at stands, engines off, or just taxiing, with their strobes on. This didn't happen before installing FSReborn Lights and I'm wondering if this a common issue with other users. 

    Any solutions to this would be greatly appreciated.

    Acer.


  9. 18 minutes ago, Bluestar said:

    I'm putting over a hundred hours a month on my P3dv4 machine (only use PMDG aircraft) and probably experience 30 sunrise/sunsets a month  and have never had a failure during these time periods. My  card is a 1070 so that may be the difference.  Technology changes from card generation to generation are tremendous and the latest graphic drivers make a big difference.   When I was running FSX I never had this experience either.  

    I never had any graphics problem in FSX in related to sunrises/sunsets. It only seems to be affected in P3D. It probably is only because of my old graphics card and I am in need of an upgrade.


  10. Hello all,

    I have a GTX 650Ti. I have set an fps limit of 30 and the GPU only utilises about 35-40% of the memory. I was flying the PMDG 777 from Heathrow to Shanghai when about 5 hours into the sim, the sun starts to set. When it comes to the sun setting or rising in the sim, the graphics card just crashes with the "DXGI_ERROR_DEVICE_HUNG". I noticed that I only get this message when the GPU utilises 100% of the memory for a long period of time but during sunset, the GPU isn't using 100% of the memory.

    I hope this isn't too vague but any help would be greatly appreciated. Also, I don't have settings put on max, they're usually set around the medium/low setting.


  11. Thanks everyone for your replies. It's sensible that the FMC would warn me of an outdated AIRAC cycle as I have been doing flights so far with the default date and time. And yes, I do use Navigraph's FMS data manager to update my AIRAC cycles. Everything is fine now since I changed the date and time to the current time that the AIRAC is meant to be used.

    Thank you guys for your responses and I hope you all have a Merry Christmas!

    Edward

    • Upvote 1

  12. Hello everyone.

    I have recently bought the PMDG 777 for P3D v4. Once installed, I double-checked that the nav data was up-to-date on my plane and sure enough it was. But what was odd about this was when I went to the "IDENT" section, I received the message saying: "NAV DATA OUT OF DATE" 

    This was strange because I looked above the message and it said that I was using the most up to date cycle which is currently 1713 as I am typing this. 

    I also checked the Navdata files in the 777 and that even says that it's on cycle 1713.

    I find it irritating and I am wondering if there are any solutions to this minor problem? Any help would be gratefully appreciated. 

    Thank you!

    Edward Berkley


  13. 4 minutes ago, Cactus521 said:

    I found I had the same thing on my old system and FSX.  Switching views I would sometimes find myself in a gray Carenado cockpit for ten or fifteen seconds.  Problem went away with my new system and P3d4.

    John

    Maybe it's time to move on? To move to a new simulator? To be honest I was planning to get p3dv4 anyway. What are your specs?

×
×
  • Create New...