Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Nick M

Commercial Member
  • Joined

  • Last visited

  1. Just a little note to let everyone know that we've just released the v1.2 update for the Comanche. 🙂 To install version 1.2, please click the "Comanche Check For Updates MSFS" shortcut in the "A2A Simulations" folder in the Windows start menu. Thanks Nick - A2A Simulations
  2. Yes, just to confirm that we are aware of a bug where a sudden, huge spike in engine torque can, very, very, very occasionally flip the entire plane the plane in the air when using the starter or when towing (the prop is actually rotated a bit when you attach the tow bar, so it doesn't make contact with it). This has resulted in one or two funny moments on livestreams, and we would like to particularly apologise to any VR simmers who have been traumatized as a result. 😁 It's been hard to reproduce, but should be fixed with the first Comanche update which we'll get out as soon as we can. Thanks, Nick - A2A Simulations
  3. Nick M changed their profile photo
  4. Thomas, I can recommend Scan (though I haven't specifically bought Saitek stuff from them). They do the ProFlight rudder pedals for around 90 quid at the moment, and the yoke for about £116. However, looks like no stock until next month. Delivery would be about a tenner by the looks of it. Nick
  5. Pe11e - just wanted to make you aware that leaving "high-resolution 3-D virtual cockpit" un-ticked will cause visual artefacts (enlarged LCD digits) on the radio stacks in the A2A Skyhawk, Cherokee and Skylane. It will also tend to cause some issues with cockpit lighting. Cheers, Nick
  6. Just a brief note to add that there's currently a small glitch with the control panel installation with v1.014 (missing bitmaps). A fix can be downloaded from the link in this post on the Majestic forums and I gather the installer will be updated within a week or so. Cheers, Nick
  7. Hi Keven, Thanks for the reply. Hope the touchdown smoke does make it into a future product: I'll certainly keep my eye out... Cheers, Nick
  8. Hello Guys! Have to confess I'm not a PrecipitFX customer (yet) but I'm certainly interested for the modest price. I have a quick question though... Does the package enhance the existing FSX touchdown tire smoke effects? As far as I can tell from the website and video, it doesn't. If this is indeed the case, is there any chance that this is something that would be considered for a future update? Maybe I'm a bit of a narcissist, but I tend to watch my landings using the replay function from time-to-time. Typically I fly GA stuff, and I've always noticed that the default FSX "fx_tchdwn_s.fx" effect is a bit odd. Specifically, the puff of smoke generated on tyre contact with paved runways seem to rise vertically whilst actually keeping pace with the aircraft (i.e. matching its forward speed) which is a bit disconcerting. Any technical insight from the FSFX experts would be very welcome. Do you guys also see the effect rendered in this way? I'm also not terribly keen on the touchdown smoke effects for larger aircraft either as they seem a bit overdone; a general overhaul of the three paved runway touchdown effects in FSX would be very welcome! :wink: Thanks, Nick
  9. Christopher, It's not a video, but I can recommend the website Flight Simulator Navigation by Charles Wood as an accessible and entertaining way to get to grips with the subject. The Duke v2 may be great, but it'll be a testing platform as a basic instrument/navigation trainer. Something with a little less performance would make your life easier. Cheers, Nick
  10. Yikes indeed! Actually, I'm not sure whether A2A's simulation of carb heat itself takes into account EGT. Maybe it's a question I should raise over on their forum. From what I've seen, applying full carb heat in the Cherokee is a rather quick and effective remedy, so probably not. Cheers, Nick
  11. I hardly think one can accuse RealAir of "using the simming community as cash cows". In fact I wish more developers would take a leaf out of their book and offer older products at a substantial discount. For example, the RealAir Legacy currently represents the best value pay-ware that can be had in my opinion. That being said, I've yet to go for the updated turbine Duke. That's largely due to the fact that I'm trying to improve my instrument flying skills is lower performance aircraft - I really don't need any more distractions! I always preferred the piston Duke as well for some reason... Cheers, Nick
  12. No - I'm with Great Ozzie on this one. The symptoms described by Elaine sound most like carburettor icing. I must admit I didn't know much about this phenomenon until flying the A2A Cherokee, but I learned a great deal from this thread on A2A's forums. As well as the temperature 'danger zone' for carb icing (well illustrated by the graph in this post by 'ft') one other thing I learned from the discussion was that carb heat should be either fully on or off. Partial carb heat application can actually make carb icing more dangerous! I'll confess I've been deliberately flying the A2A Cherokee in conditions conducive to severe carb icing (e.g. temp and dew point of around 5 to 6°C) to experience some of the simulated 'Accu-Sim' effects. For example, carb icing with high (cruise) RPM as Elaine describes is certainly possible, and it can start of as quite a subtle and insidious power loss. On the other hand, selecting full power after a descent at idle can result in... Well absolutely nothing - no power at all - until carb heat is applied. Of course, improper leaning on the ground can foul the spark plugs, but this will generally be cleared up by running at reasonably high RPM for a while. In other words, if you survive the take-off and climb out with fouled plugs, you'll probably be okay. I couldn't agree more! :smile: Cheers, Nick
  13. I'd love to think so! However, I recently reinstalled my copy of FSX and the frame-rate drop with complex add-on aircraft was apparent from the outset. While my system is not that recent ([email protected], EVGA GTX570) it's generally pretty adequate for running FSX, and I have't got a host of other add-ons. I think it's likely that the increasing complexity of internal MDL files is the culprit. Perhaps the way that click-spot functionality and animations are encoded into the MDL file? However, some of the add-ons that I use seem to suffer the problem more disproportionately than others. I've noticed the frame-rate drop is more noticeable when the sim is being worked hard, and I wonder if the explains the OP's post? i.e. If Glenn's PC is now having to work harder (perhaps due to an additional add-on), the mouse cursor effect could be the 'final straw' that's pushing his FPS below the locked value. Cheers, Nick
  14. Yes, although oddly it's still seems to rather poorly understood and documented. I say 'oddly' because on my system it's very easy to reproduce and I'll typically lose around a quarter to a third of my FPS due to this 'bug' in the more complex add-ons. I don't think it is a rendering issue as such Martin. Instead, I reckon the FPS drop is caused by the fact that the simulator is performing calculation based upon where the cursor is and how the it interacts with switches and buttons in the VC. I'm basing this idea on some observations in this thread in the A2A forums. It's generally noted that if the cursor is visible but it's superimposed over either a 2D window or the FSX title bar, FPS are unaffected. I've also noticed that if you view the VC in 'cockpit' mode rather than 'virtual cockpit' view (I have to glance to the side to actually see the VC in this mode) FPS are unaffected whether-or-not the cursor is visible. Crucially, in both of these cases, the cursor is visible in the VC but without the click spots being 'enabled' and (on my system anyway) FPS are unaffected. This seems to suggest that it's a 'VC clickspot interactivity issue' which is causing the FPS hit. I'd certainly welcome any more input on this topic - particularly from add-on developers. It does seem to be one of the last great FSX mysteries! :huh: Cheers, Nick
  15. Yes - that's very true as well! I'm no purist and will quite often exit the sim with the Cherokee parked-up with the engine running, flaps set and so on. When I next load the aircraft, everything is remembered, so I can basically just carry on where I left off. Accu-Sim certainly isn't all about damage, wear-and-tear and pesky maintenance. For me anyway, it's more to do with convincing behaviour of the instruments (instruments which are actually worth bothering to monitor), immersive sounds and the feeling that the aeroplane has a bit of unique character. Cheers, Nick
  16. Hey Craig - glad you've seen the light! :smile: The A2A Cherokee certainly wins the award in my opinion and I try not to miss any opportunity to evangelise about it! It's such a charming little aeroplane which is perfect for a cross-country adventure or just a few circuits at the local aerodrome. Beautiful three-dimensional visuals, bewitching sounds, fantastic custom avionics/gauges and the overall Accu-Sim immersiveness that you describe. I could go on, but I sense eyes glazing over... :wink: The Majestic Q400 takes a close second place for me and is perhaps the winner of the 'finest technical achievement' category. I still find its performance in the sim absolutely staggering... My vote for 'best value add-on' would have to go to the RealAir Lancair Legacy: I love it and I wish more developers would discount slightly older products in this way (even though I bought it a full price). Nice thread - don't we simmers just love to vote for things! Cheers, Nick

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.