Recently we have seen a lot of codes used to unlock our products being offered for discounted prices. Almost all of them are bought using stolen credit cards. These codes will all be blocked by our systems and you will have to try to get your money back from the seller, we are unable to assist in these matters. Do be very careful when you see a deal that is almost too good to be true, it probably is too good to be true.

Jump to content

por928

members
  • Content Count

    167
  • Joined

  • Last visited

Community Reputation

65 Excellent

1 Follower

About por928

  • Rank
    Flight Student - Solo

Recent Profile Visitors

1517 profile views
  1. Hans, very good that you have found an issue that may assist us with flight save/reload.. Can you comment about the current/previous AIRAC dates and how, if at all, they affect the save/reload flight. For example, if i save the flight with AIRAC "A" but reload with AIRAC "B"? As long as the waypoints are the same, does the AIRAC date have any effect? Did you find any difference between Nav database providers? I would imagine most of flights saved would have had FMS data of some sort incorporated. In my case, as you know, the action of reload of a saved flight, would kill off my P3D session, so I am hoping the Dev version and your latest fix will solve my issue as well. When you release the fix and hopefully, newer version, I will test the various permutations and see if I can get this matter resolved.
  2. I was in cruise at FL380, some 5 hours into a 7 hour flight(KJFK-EGLC) with no action on the stick(Logitech Extr 30 Pro, using Chaseplane. I notes there are several posts scattered about the forum. To me, it is like the aircraft has run out of fuel and flattened the batteries (despite loads of fuel on board) the aircraft systems just shut down, in my case, the packs went, then the gens then a few moments later, all black. When I was just getting out the life jackets, when at about FL120, she came back to life, with no FMS loaded...
  3. Umm, and I thought I had done something....On a long flight BAW2, KJFK-EGLC with the A318(BA Livery) and just short of Shannon, I just lost all power including electrics, in the night with nothing on the screens....A tad scary, as no RAT, no emergency power. I first noticed pack 2 fault, then pack1 then the gens off line...sort of like fuel starvation, though FOB=7280kg... But after descending from FL380 through 9000, all of a sudden, everything came back to life..Though, the flight plan was lost. Now diverting to EGAA and will land here and give most of my passengers some Valium, then re-schedule the flight later today. First time ever this happen with the buses.
  4. Hi Hans, So, you managed to load that YBBN YSCB file, fly for 5 minutes or so, then save the file via the Scenario tab. Close P3D, open P3D, and reload the saved flight with no issues. It is one of those things. All our machines are slightly different. The majority of PC's are similar enough that their Win 10 and P3D and the Aerosoft CRJ build are within your machines allowable code range. I just need to park the CRJ and wait until the coding becomes broad enough to cope with my machine's combination. I just carried out the YBBN-YSCB flight plan and my dog harassed me for some thing at the crucial moment as I was on short final, only to lose too much airspeed and stalled when I looked back. Normally, I save my flights when in cruise and just before TOD. Obviously I could not do that in this case. Again, thanks for trying.
  5. Hi Hans, thank you for reply. Here are the files i had created for the test...For me, they do not even look like loading. CRJ 700 YBBN YSCB2.fxml CRJ 700 YBBN YSCB2.wx CRJ 700 YBBN YSCB2.crj CRJ 700 YBBN YSCB2.crjfms
  6. OK, when I created and saved the scenario, then tried to reload it, it crashed P3D. Several attempts all had the same outcome. Sometimes to the screen saver some times the load hangs requiring me to crash out. For some reason, despite the two updates, that previously allowed me to load a saved scenario, have now stopped working. All other aspects of the aircraft seem to work great. When I reload a saved scenario for the A318-A321, I have no issues. The same for the FSL A320, the PMDG 777, the majestic Q400..all load ok.
  7. That's ok Tom. If the Updater says it has updated the a/c to what ever x.x.x, then that will do.
  8. As stated previously, I Updated the CRJ700/900 to 1.2.0.0. and applied the Updater for the CABIN ALT and PASS OXY ON warning. On the same day, with no P3D restart, when I saved a flight and reloaded it, the scenario was correctly loaded. and I could carry on with the flight. However, after a restart of my P3D machine, and I reload P3D and try and load the same saved flight, it crashes P3D...either straight to the screen saver or it might hang unresponsive and needs me to use Task Manager and end task. Anyway.........Later, I will create a flight plan and configure the CRJ900 again for taxi, sitting at an airport. Save it, and while P3D still running, reload it. Assuming it loads ok, I will then reboot the P3D machine and retry loading the scenario and see what happens and report back. I have been playing with the Updater, so I am not sure if this has upset it. My method of reloading a scenario is to: Load P3D>at the load screen, accept the default a/c(F22) which has its engines running, and accept the default airport, select ok, and when the F22 is sitting at the end of the default runway, I select Scenario from the top left, and select load. Chose the saved flight scenario, click ok. Maybe my machine is sensitive to this reload action. I recently had the P3D QW 787...For me, the major issue was being unable to get the saved flight scenario to reload. Apparently some QW 787 people did not have any issues. There was another group of us that did have this issue.
  9. OK, looking at my original questions. In my Programs and Features area, the Version loaded does not reflect the changes made by the Updater!!! I guess this is to do with the actual base program loaded and the changes made to the base program are sort of hotpacks? Does it matter where I run the ASUpdater from? It does not seem to matter. I tried different location Updaters for the CRJ and the A318-A319, and both report the changes were made. I thought at one stage, the Updated was located in my A320 program list. Maybe as Otto said, it gets Win 10 a tad confused if the Updater's are in the same area. So, all is well in the Updater camp, and everything clarified. ✔️ Thanks for the replies guys.
  10. That file crj700900x_p3d4.xml was there.
  11. Hi Otto, What are we looking for when I open the updater? I see my version = v1.1.8.0 it says P3D 4.x found it comments that it found the Add-on Path for the A318_A319 it comments that it found the Add-on Path for the A312_A321 It does not comment it found the Add-on Path for the CRJ It works ok, (well it says the update went ok) from any of the sources I find it on my system.
  12. I notice the Updater is located in my program list CRJ>Run Updater, my Start Area, and Documents>Aerosoft>ASUpdater. And in this location, I can see the Log files showing the updates...A318-A319 and A320-A321 to 1.2.1.3 and my CRJ to 1.2.2.1. When I look at the add programs, it still refers to the original load versions...e.g..Airbuses =1.0 and the CRJ=1.2.0.0? How can I check what version is actually loaded? Does it matter where I run the ASUpdater from? I thought at one stage, the Updated was located in my A320 program list.. I notice there is also a Documents>Aerosoft>ASUpdaterUpdater.exe....which relies upon the Updater.exe.
  13. Hi Hans, Sorry, I must have explained myself wrongly. The fix you recommended in your first post worked. I did update the a/c to SP1 and I did use the updater to add the repair for the CABIN ALT and PASS OXY warning. The Save and Reload the Flight Scenario now works, with one issue. When I reloaded the Flight Scenario, On the PFD, the next waypoint is flashing and a bipping sound. I have seen this before. Why is it some times setting up the flight plan and cockpit settings, on the PFD, under the V speeds, the first waypoint is flashing all the time, in my case, 34.0NM CMSKY. When I pass that waypoint, it stops flashing when the new waypoint to come is displayed. Subsequent waypoints do not flash. I notice when I select other than FMS1/2 the flashing stops, but I lose the Nav control for the flight plan. The CABIN ALT and PASS OXY ON warning no longer appears. so this is fixed.
  14. Hi Hans, I did two changes before I retested the flight plan scenario load. Updated the CRJ700/900 to 1.2.0.0. Set up a flight from KORD to KMEM and as I was climbing out and at 20,000+ feet, I got a CABIN ALT and PASS OXY ON warning...so, a bit of searching in the Aerosoft Forum, and I found there was an update for this issue on the updater-experimental. carried out the update. Before I created the test flight, I loaded the default a/c and the default airport as usual, then thought, ummm, I have a few saved flights with the CRJ700, load one to save me having to rebuild the flight plan and aircraft config etc now that I have the SP1 build....NAH....Every load of saved scenario's crashed P3D. Maybe P3D sees the saved scenario's from a different version of the CRJ700 as different builds and not happy to load them? Ok, Observations about the flight. The flight I created is now passing through 32000 and no CABIN ALT and PASS OXY ON warning. Great. Fixed. I saved the flight at cruising. Then closed P3D. Rebooted P3D, loaded the default a/c and airport. Used the P3D Scenario tab and loaded the saved flight. It loaded pretty good with all engines and settings the same.The Flight plan was in place and active. I did have one issue. On the PFD, the next waypoint is flashing and a bipping sound. Why is it some times setting up the flight plan and cockpit settings, on the PFD, under the V speeds, the first waypoint is flashing all the time, in my case, 34.0NM CMSKY. When I pass that waypoint, it stops flashing when the new waypoint to come is displayed. Subsequent waypoints do not flash. I notice when I select other than FMS1/2 the flashing stops, but I lose the Nav control for the flight plan.
  15. I have a P3Dv4.3 machine and have the CRJ 700/900 v 1.0.5.0 loaded. Just started flying the little girl. Steadily getting there. When I save the flight and reload that flight following a reboot a few hours later, I lose the FMS info. The flight setup seems ok, and in for a wild ride on startup, and then starts to return to its previous level. I fire up P3D, always load the default F22 and the airport. With the default sitting on the runway, I then use the P3D Scenario>Load>(find the saved flight, it has a .fxml ext) click OK . When loaded, I can see the aircraft is at the correct flight level, and on my littlenavmap and it is in the correct position. We go into a extreme climb with the previous alt flashing, With no flight plan loaded, we are not going anywhere.... What am I missing on the save/reload to get my saved flight working.
×
×
  • Create New...