Community Discussion > Flight Operations
Historic Dutch East Indies Route Event - Reports
EHM-1442 Luis:
Hi
My problems had started before the start line for the Historic Dutch Indies event.
There is a basic rule that says- if your system is running well, don't modify it just before an propilot event - But i didn't care about this rule and i changed my cpu and ram.
CPU – Intel Q9550 and RAM – 4GB
I run XP 32 bits and FSX sp3. Notice that XP has a problem to manage 4gb of ram.
I made about10 attempts to finish the first leg and after 10 or 15 minutes flying i received an error message “Run out of available memory.....blah...blah” and fsx crash to desktop.
After the ctd, I did some googling and I modified the page file, new attempt, new crash...modified the settings on fsx, new attempt, new crash.... I found the solution on this SimForums with the boot.ini modification. http://www.simforums.com/forums/forum_posts.asp?TID=29041
I hope this can help other people.
No problems on the first leg.
Leg 01 – Leaving EHAM
http://i233.photobucket.com/albums/ee6/Filipe974/EHAM01.gif
http://i233.photobucket.com/albums/ee6/Filipe974/EHAM02.jpg
Leg01 – Arriving LFMV
http://i233.photobucket.com/albums/ee6/Filipe974/LFMV01.gif
http://i233.photobucket.com/albums/ee6/Filipe974/LFMV02.gif
Comments and reports from other pilots are welcome
Cheers
Luis
EHM-1001 Robert:
Oh Luis,
I am really sorry about you. The good'ol XP can handle only 3.2 GB of RAM, so practically 3 modules... which can be unstable if you not use pairs... If you have asked about it, we could have answered it.
Better luck next time, and happy flying !
EHM-2387 Eric-Jan:
Hi Luis,
glad you worked things out and got your system up and running again! And thanks for the link to this very useful FSX tweaking site. I hadn't seen it before. It contains a bunch of useful tips and tricks, which I will be needing soon when I am done saving up for my new PC (Updating for me would mean CPU => Motherboard, RAM, HDD; in short: total system replacement). Advantage for me is that I will be having two systems to choose from for a while, until the wife confiscates the "old" one ;)
Anyway: a good idea to open up a thread for flight reports. I will certainly post some of my adventures here.
Like this leg one:
I am still getting to grips with the F100. I thought she would be more or less over powered, but much to my surprise, I keep finding myself taking off at the very end of those sometimes looong runways... So I decided to fly the first few legs off-line until I am more comfortable and confident that I'll find all buttons to push when I need them. I do use dynamic real world weather, and for this first leg I used daylight time, just to be able to enjoy the surroundings more.
I looked up the runways in use, and decided on rwy24, LEKKO1S departure. Dialed in the appropriate frequencies, and fired her up. After taxi to S7 I was immediately cleared for take off (I still had AI traffic to 0 ...) and I managed to take off, keep her under 220 KIAS, turn left as per SID, and follow the SID to LEKKO. From there it was an "easy" GPS autopilot flight to LFMV. More or less...
I liked the view of Paris from FL330. Makes you realise that Charles de Gaulle airport is really BIG !
After a small hour or so, it was time to initiate descend. Passing through different key altitudes, I "suffered" for very rapidly changing wind diractions, so I put my AP IAS to 200 kts, just to be sure I would not hit that overspeed below FL100 penalty. I had my descend planning set up to arrive at AVN VOR at 8000ft. Then I peformed a hold as published, while descending to 3000ft, then on to AN (over the field, and follow the outbound radial 005 for 7nm. Turn left to intercept ILS 17. All went OK (much to my surprise) until then. I was pretty pleased with myself not having hit any penalties yet, when I pressed the button on my throttle quadrant to lower the gear. Immediately a green strip on top of the screen, announcing the "Landing lights off under FL100" penalty. Grrrrr...., pushed the wrong button. Pushed it again, and then pushed the right button to lower the gear. Ah, well, such is life; you give some, you take some.
Meanwhile I was established nicely on the localiser. Last check: lights on, gear down, altimeter set correctly, lateral position on course 169 to localiser, vertical position on glide-scope, airspeed OK, runway in sight ... All set for a safe landing. Some crosswind, but not too much. This should be a walk in the park.
When almost over the threshold, AP off, reduce thrust, up the pitch a notch, and BOOM, the wind had turned from a 20 kts headwind into an 10 kts tailwind. Thus reducing my IAS from about 140 to 110. BANG, on the tarmac. Both penalties for excessive G-forces, totaling up to 900 PP penalty points. With the 150 of the landing lights I even got to 1050 ::)
Lucky I did not crash the plane, or I would be out of the event already after one leg ...
Next leg, to LIRN, I will probably fly tomorrow. I also want to install the DA F100 for FSX (and get to know that one a bit too, first), so I'm not sure which one I'll do first...
See y'all up there!
Eric-Jan
PS: next leg I'll shoot some pictures too ;)
EHM-1749 Hector:
Following Luis idea to open this section, I am switching to it.
For the second night (early morning in Europe) in a row I flew leg 1. This time I wanted to be sure my flight was not unlocked. But after finishiing it again the same problem with the EHM website. I could not send the PIREP to EHM. It is saved but not sent. Again the home page was not fully shown. It only opened down to the 10 top PP pilots. Nothing on actual flights nor last PIREPs reported. Could it be that at that particular time the site is slower for maintenance purposes?
Are there other pilots suffering of the same problem when flying between 0200 and 0400 UTC?
Oh! in this flight I noticed something that had never happened before: The strip announcing the actions was delayed. I noticed when setting the flaps before takeoff. I took like a minute to show up after the action was taking. And the gear down confirmation was almost at touchdown no matter I normally lower the gear when passing 1300' altitude.
My first flight was between 0330 and 0500 UTC on Dec 19. Today, Dec 20th, my flight was between 0200 and 0400 UTC. Rem my local time is UTC - 4.5
So I have flown the leg twice but still in EHAM.
One thing is for sure. It is not my machine because I could again sent the PIREP to IVAO just like always.
I will try again today. At the same time.
Finally, this is the message I got when pushed the PIREP sending key:
"<HTML><META HTTP-EQUIV="content-type" CONTENT="text/html;charset=utf-8">
ERROR: MDB2 Error: unknown error :: connect: [Error message: User euroharm_ehm03
already has more than 'max_user_connections' active connections] [Native code:
1203] [Native message: User euroharm_ehm03 already has more than
'max_user_connections' active connections]"
EHM-1001 Robert:
Hi Eric-Jan,
Try remove the extra Cargo from the payload list, and apply more trim at take-off. Unfortunately I had to fly twice the flight, because I could not send in the PIREP - I got the same error message.
Now flying the 2nd leg over the Riviera. Too bad it is winter season and only 10°C down :)
Navigation
[0] Message Index
[#] Next page
Go to full version