Have you ever wondered what it would be like to have a private island with small airport? Well, if you are something like me (and probably most of people), you can turn this in reality if you happen to continue working like another 2000 years. But luckily, we have a virtual world within our favorite flight simulators, where the costs of work, building materials and last, but not least, the island itself, are kind of insignificant.
So here I come with my freeware scenery project – the Mouseviator Private Island scenery. As name suggests, it is a scenery of small private island I made for myself (and for others to visit) for FSX and Prepar3D. If you are interested, pay a visit to this festival of wasted money (as I would call the island if I would be building it in real life ;)).
in this post, you can download a free fictional repaint of VFD Čelákovice for Aerosoft DHC-6 Twin Otter Extended – version 300 amphibian. The aircraft registration is OK-DHC (DHC is a shortcut Celakovice Volunteer Fire Department in Czech language and a nice coincidence it is also the shortcut of aircraft manufacturer: de Havilland Aircraft of Canada Ltd. :)).
in this post, you can download a free fictional repaint of VFD Čelákovice for Cessna 172 Trainer aircraft developed by A2A Simulations. Four variants in total are available. There are two country variants, one with Czech registration and one with American registration. The Czech registration is OK-CVF (CVF stands for Celakovice Volunteer Firefighter). American registration is N450VF (VF stand for Volunteer Firefighter). Each of the country variants have two colour variants – one with blue stripe and one with red stripe.
In this post I would like to share some checklists that I have made for aircraft’s I like to fly in Flight Simulator X and/or Prepar3D. Well, I did not made them in the way of inventing them. I build them upon documentation that came with respective pay-ware aircrafts that I own. There are a lot of checklists available out there on the Internet, why should I be interested in those, you ask? The truth is, you don’t really have to. Continue reading →
Hello, maybe you have noticed, maybe not, but the development of EZCA has been resumed. As for the date of this update, there is version 1.18.5 BETA of EZCA available here: EZCA 1.18.5 Beta Available for Download. This new version works with TrackIR interface differently and it seems it eliminates the bug this whole post is about = it now works with FreeTrack without crashing (making my solution redundant). Ok, at least it works for me. It is BETA though, it might bring another issues for you. (I use mainly virtual cockpit views and access them via shortcuts and have no problem with this). So if anyone interested, check out the link above, read through it and decide if you want to try it.
At first, I did not want to invest any more time into that EZCA issue, as it would be definitely cheaper to buy TrackIR and have no issues rather than trying to solve all the problems arising from concurrent FreeTrack and EZCA usage. But I discovered the “power” that we have thanks to Lua – thanks to its integration within FSUIPC. Thank you Peter Dowson!!! And so the curiosity and my passion to learn new things won again. Continue reading →
I have not been using my EZCA restart script for some time and … I started to do again. I was little surprised when it turned out that it does NOT work anymore for some reason. EZCA just continued to eat memory until it crashed again. However, it did not throw millions of error messages on me, just closed itself (this counts to the fact that it is was EZCA P3D beta build). So I started to investigate and found out, that my approach to monitor EZCA memory consumption was not the best one. (This only happens if you use EZCA_RESTART_BY_MEM_LIMIT option). So I changed the approach to monitor EZCA memory consumption.
Simply saying, the script now saves current EZCA memory usage to file called: ezca_private_bytes.txt. So you can look there. When the script runs, the difference between actual memory consumption and saved memory consumption is calculated. This difference is than added to current memory consumption and the result is treated as future memory consumption. The script than checks if future memory consumption is less than defined safety value and continues to restart EZCA if it is not.
Some constants were also removed due to the change described above. Please see the .CHANGES section in the script comment for more details. Also, look at the detailed description of the script in the previous post: Flight Simulator X, EZCA and FreeTrack.
You can download the script here:
EZCA Camera for FSX restart script v 1.1 21.43 KB (435x downloads)
If you are running all three mentioned in the title, you probably have a problem. The problem is that EZCA and FreeTrack kind of don’t like each other. When EZCA and FreeTrack are running together (at the same time), EZCA will crash after some time. Usually, it takes between 10-25 minutes. As the result, you will get a bunch of error messages related to memory access violation.