Jarkko

OK, So the real world weather was that I should takeoff in VFR conditions and land in IFR conditions. You make up your mind if this was the case TAKEOFF AND CLIMB: Turning to line up runway 18: Looking back at KUTS: Climbing to 18000: Where did the land go? CRUISE AND DESCENT: You can see Dallas out the left window: Still VFR? Nope, I don't think so. Looking very good!

Hello again! Back from the second run (nice one, I may add). Here is what I "found". All winshear and preasure "events" stopped when I descended below 2000 AGL. Lower than that, the preasure stayed locked at 1022, which was the exact number in the ATIS. 2000 AGL happens to be the value I set for "Assume Cruising above" value. My "Disable Updates when Below" was 1800ft AGL. Where did that come from (part 2)? Only asking if this is a feature (other have seen it and all is fine) or is this a bug (wow, haven't seen that before, thanks for the heads up). Anywhoo... Another very nice flight! Excelent weather. I'll soon post screenshots (even though I messed up the approach while looking at my laptop). Overcast was truly beatifull. The Live camere added yet another level of realism to the flight!

No quite. I'll give you a hint. FSX doesn't run on Linux. That's all folks, nothing to see here

Thank you for the replies! I'm off to do another test flight (I try to take screenshots, because the weather was beatiful last time!). I read all the manuals ~3 times before and read all FAQs I could find. This still doesn't mean that I didn't make a mistake along the way. I might have forgotten to input cruising altitude by accident. I'll double check everything. What? Where did that come from? When have I ever said that I was developing anything for FSX? Anywhoo... I'll take screenshots so that we can verify that I'm not doing something wrong. Regarding the monitoring program (FS Flight Keeper). Unfortunately I can't disable it as it sends data to my virtual airline. As this was my first OpusFSX flight, the cause is more than likely user error. Thanks!

Hello! I decided to purchase OpusFSX today to see what I have been missing. I just completed my first test flight. I flew a route with two other weather engines that I have used prior to OpusFSX. Then used OpusFSX for the same flight. I'll first explain the test scenario and then my findings. (tldr -> Very good but annoying flight): ----- TEST SCENARIO: Flight from KUTS to KDFW. Date: 2013-01-25 (yesterday -> historic weather). Time: 17:15 UTC/Zulu. Airchaft: JS41, Fuel: 3000lbs, Payload: 0lbs. Route: DCT LOA LOA.CQY6.ILS17L (wanted to test tailwind landing a flying from VFR to IFR conditions) Here is the real world weather for the flight (numbers and colors show ceiling): Departure METAR (during planning/release): KUTS 251653Z AUTO 21010G14KT 10SM FEW027 22/14 A3018 RMK AO2 SLP215 T02170139 Destination METAR (during planning/release): KDFW 251653Z 02012KT 7SM OVC006 08/06 A3019 RMK AO2 SLP221 T00830056 ---- RESULTS: The transition from VFR conditions to the expected IFR conditions was better than I have ever seen. One other product does this quite nicely, but my first impression is that OpusFSX does this in a way that feels more realistic (at least to me). In grades from 1 to 10, I would score "other" product 7+ and OpusFSX 9 (you will soon find out why only 9) Just for comparison. Here are the OpusFSX generated weather conditions for departure and destination. Departure METAR (actual/OpusFSX generated): KUTS 251722Z 21310G14KT 9999 FEW030CU FEW400CI 22/14 Q1022 Destination METAR (actual/OpusFSX generated): KDFW 251836Z 00411KT 8046 OVC011ST FEW402CI 9/6 Q1022 Very good I would say! ---- PROBLEMS: During the flight, I was getting constant problems with windshear and outside preasure changes. I have yet to experience this kind of behavior with other weather engines. Here's a picture from FS Flight Keeper: The important columns are Type, Event and time. Look closely at the lines with type "Windshear" and "Preasure". You should see that during a span of 10 minutes they change quite frequently. FS flight keeper keeps nacking me about these changes. For example: preasure change from 1022.7 to 1023.0 => "Please check you altimiter setting". I heard A LOT of these during the trip Also for every windshear I receive this: "I don't like that wind, I think it's shearing". Had a lot of thos too. ----- QUESTION: Is this by design or is this possibly a bug? Preasure changes from 1022.7 to 1023.0 (delta: 0.3) seem quite small to warrant to be sent to FSX. Also the windshear was extremely "forcefull" from time to time. Thanks for the help! (I'm off to test the camera system)

TOC and TOD calculation based on adjustable flight path angle, automatic flight logging, safe altitudes on charts, color codes for surrounding airports with or without instrument approach, remaining endurance prediction, heading to the nearest user selected enroute alternate and user customizable check lists. Also having a moving aircraft on the approach plate (both top down and side view a.k.a descent path) helps in all too familiar situation where FSX ILS is missing or "INOP". I might forget something but these help a lot

First things first. Sorry for "hijacking" this thread. I considered that it might be "acceptable" as the OP has received an answer on the official support forum. (Not a bug in OpusFSX but a misunderstanding). Thank you Stephen! Now I have something I can use to evaluate the demo version. It easier when you know what to look for. Much appreciated! This was not my intention. I'm sorry if it can be seen as such :( I was just reporting my own findings. The good think is that the weekend is here and I have time to take the OpusFSX demo for a spin

Navigation databases are updated every 28 days. Each 28 day period is called an Airac cycle. In real world, I should only use the latest released cycle. Now where can one get the updated Navdata for each cycle? You can buy each cycle from either Navigraph or AeroSoft (NavData Pro). Hope this helps (without explaining all the things that are included in the Navdata)!

Hello! If you read the pinned FAQ topic found here: http://forum.avsim.n...pic/396956-faq/ you'll find out that Opus doesn't provide textures but works well with free and payware textures (REXE being one of them). From what I have seen, Opus produces overcast conditions and chancing weather really well. A lot better than REXE at the moment. I would suggest that you also visit the official Opus forum to see what is available now and what thinks are planned for future releases. Opus releases updates a staggering speed. This should help you see what works for you. Happy flying!

What I forgot to say is that Opus has every right to be proud of their product. Like many have said, it's one of the best things released in a long time. I just wish that comparisons to other products would be based on true data.

Thank you for your answer! I think I didn't quite ask the question correctly (English is only one of the four languages I try to speak). If you don't mind, I would like to try again. I tried to challenge this statement. From my flights and the screenshots I've provided, you should see that this is not quite true. Very good. Both programs do almost the same think. The difference (at least for me) is that Opus injects weather beyond the 80 miles mark. With both programs you can see the weather approaching, weather to the sides and the weather you left behind. Absolutely correct. This is why both of the products provide "ATIS enhancement". Opus has the dedicated window and AS has a set of frequencies you can set you radio to listen for correct ATIS. I prefer the Opus way as you can use the window _and_ correct ATIS frequencies. Our weather is not morphed to anything like the same extent. Most likely the worst that will happen is that FSX will decide to place a cloud layer 100 or so feet different than specified when nearly 300 miles away ! When you inject METARs (as Opus does NOT do) then the weather can be seriously morphed right in front of your eyes (Stephen). What I'm trying to say that I have yet to understand what is behind these words: "you don't see realistic weather". I know that the analogy police will arrest me but _to me_ this sounds equivalent of Wilco saying that PMDG's 737 doesn't have an autopilot. It is very likely that I have misunderstood something. This is why I'm eager to learn more.

Hello! This got me interested. Can you please expend on this? Just to compare, the first post has 6 pictures. http://forum.avsim.net/topic/396396-as2012-took-my-breath-away/ On the picture #4, you can see that there is clear weather in front of the aircraft, but clouds to the left and overcast behind the aircraft. This was using the Global/direct weather mode. How does this differ from the way Opus injects varying weather around the aircraft? Thanks for the help!

My vote goes to PFPX. There is no release date, but my guess is that it's 2 and a half months away (Just a future customer, no connection to PFPX. Only a pure guess).

Here's my perspective (that I already posted on AoA forum): "Time to reflect. What has happened in the last 15 months? Bought the 737 captain package ($80), thought about having a baby, had a baby, baby got her first teeth at the age of 4 months. Oh, I almost forgot! First 737 flight video was released and none of the content for the captain package." I still stand by these words (even though they sound quite bitter). Lets just say that I didn't take the 777 news well. I just wish I would have slept on it. I might have been able to express my thoughts/feelings better. Having said that and having read Chris' mail on this topic (that unfortunately was erased during database restoration), I do believe in giving a second chance. I have owned all AoA videos and more than likely, I will be buying the 777 training.

Ok, you got the airbus working. That's good! Before you do a full system reinstall, please look at these posts: http://forum.iemit.com/Default.aspx?g=posts&t=6750 and http://forum.zotora.net/Default.aspx?g=posts&m=35325 and http://forum.zotora.net/Default.aspx?g=posts&t=5213 Most of it is for win7/Vista users, but it still might help.

This is for the airbus and info picked from Wilco site: http://www.wilcopub.com/simulator-add-on/modern-airliner/airbus-series-evolution-vol1.html Under "If you experience strange behavior or CTD (crash to desktop)": Delete the "fmgc.cfg" file located in the \FeelThere\Airbus\Fmgc\A320 directory. Another one will be created automatically at your next flight. Removing this file is especially important if you have updated the navigation database with a different AIRAC cycle.

I had similar problem when I changed my units (might have been from kilograms to pounds). FSX would always crash when starting a flight. Not sure if this is the same case with you as you did a clean install (deleted all FSX related folders. I believe the there are at least 3 of them). If you wan't to try, there is a post (somewhere) on the Wilco site that tells you the file you should remove in order to avoid crashes (after changing the used units in the Wilco main panel). EDIT: http://forums.vatsim.net/viewtopic.php?f=8&t=51684 "I've reviewed the Wilco support pages, and I've deleted the FMGC file mentioned with no luck" I didn't delete the file, but renamed it to something that Wilco will not understand. This worked for me.

Sorry for going of topic, but I haven't had such problems unless there are bugs in the Navdata. Navdata isn't provided by Aivlasoft. I personally use EFB to see what my standby frequency should be (and place it in well in advance). Saves a lot of valuable time.

This is the cargo capasity for the AI-pilots. The calculation goes something like this: MTOW - fuel weight with all tanks full - empty weight = Cargo capasity. When you fly the plane, you are not limited by the cargo capasity. You are only limited by the MTOW => load less fuel, carry more cargo. Now that you have the Concorde imported, there is a way to help other AirHaulers. I don't think that I've seen many Concordes used. You could post the Concorde figures on these threads: Cost: http://forum.justflight.com/forum_posts.asp?TID=6639 Performance: http://forum.justflight.com/forum_posts.asp?TID=5705&PN=8 These will the end up in here for others users to see: http://www.airhauler.net/portal/ (stats page => reference) Thanks!

I think that we, the customers, played a small part in this product being released ahead of time. After the original (September) release date was missed, the "are we there yet" posts filled the Aerosoft forum. Can't even remember how may of these post were made. It was a lot! Aerosoft wasn't willing to release the product in it's "raw" state, but customers were insisting that we could live with bugs as long as service packs are planned to be released frequently. Well here we are. Product released and fixes are rolling. I think that within a month or two, we should be getting close the the product that Aerosoft might have wanted to release in the first place.

I think the problem is that the server/FSX computer is missing SimConnet. Client computer might now have SimConnect installed by Latitude. Could this be solved by installing Latitude on the FSX computer? Then both machines would have SimConnect? After that you could only use Latitude on the client machine, maybe.

I just realized the I didn't list FSX GO. I couldn't live without it (well I could but it's a real time saver).

That's kind of sad to hear. I'm not a Opus customer (yet), but I'm very much interested because of the exceptional customer support they provide.

In case you have used Aivlasoft EFB or Flight Keeper during one of the flights, you would already have the needed data for my first suggestion. It took me a little while to figure out that EFB creates a PDF flight log of every flight.

Hello! I usually do a couple of flights and mark down the off and on fuels + times. This can then be used to calculate the average fuel burn for the trip. One other way is to do a "one minute test". At cruise, mark down the current amount of fuel. After you have flow for one minute, mark down the current fuel. Calculate the consumption and multiply by 60. This gives you a rough estimate of the consumption.