ilias.tselios

Which one? Though I think all are renders!

We have in the cockpit a rough 3D object, to get the "feeling" how it will look, where to put it, etc. All the options are still on the table. We might just have a click spot for the 2D pop up and nothing more. Sent from my iPhone using Tapatalk

Given the opportunity I would like to address everything about the chapter "Navigation Equipment" of this project: 1. This project is based on DC-9-30 series, more exactly DC-9-32. Since we are hunting accuracy, we have to focus to a very specific model to get it right. 2. As result of #1, the navigation equipment will be as it was on the original DC-9-32. No FMC/FMS/CIVA....LORAN-C, you name it! 3. But, this will be flown today (ok, not literally today...when it will be ready) and many people might want to fly with that bird over VATSIM/IVAO/Pilotedge networks and they would like to have either the ability to follow RNAV procedures, fly a route without making a ton of VOR intersections, or even have a kind of backup means to learn to fly with VOR-only without get lost. So, for the reasons above, we decided that will make available the default GNS430. We do not intent to develop any more complete GNS. It is out the scope of this aircraft's development. We think that the default GNSs are more than enough to fulfill the above. Regards

Dear pilots, We have reached a point that we are almost finished with all mesh works! We turned O'Hare to a big building site, but I think for a good reason. Our determination to provide you the most "real" environment, drove us to overcome some tough obstacles in our way. For example, KORD sits on to mesh tiles (+41-088 and +42-088) which had gaps (!) by default between them! We fixed that, though it required us to learn to use a different 3D application to do so. The images are a rough preview of some of the edits we have done. Still remains a lot work to do, but at this point we have accomplished a major milestone on the project! Enjoy!

I really try to see something that is not achievable today be X-Plane, and I cannot. I will not even mentioned what can be done when (probably) X-Plane adopts Vulcan.

Check this: http://forums.x-pilot.com/topic/2611-x-plane-10-scenery-q-a/page-4#entry52308

You're welcomed! Sent from my iPhone using Tapatalk

We have already publish 2 European Airports: Mykonos Airport and island: http://forums.x-pilot.com/topic/5382-idt-mykonos-international-airport-lgmk/ Manchester Airport: http://forums.x-pilot.com/topic/7048-egcc-manchester-airport-aerosofticarus-development-team/ O'Hare is our next. We also developing the DC-9 aircraft. Further than that, we have a lot of plans in our heads but nothing solid.

Dear friends, We would like to thank you all for your support in 2015! In this year we were extremely happy to have our Manchester Airport published, and honoured by many reviewers as the Best Scenery for X-Plane in 2015! We will continue in 2016 with a stronger team and more passion to work on our current projects, Chicago O'Hare Intl Airport, and our DC-9 aircraft! We would like to wish to you and your families, Merry Christmas and Happy New Year!

The biggest 1920x1080 you can get. Going higher in resolution, will require from GPU to fill a ton more pixels per frame. A big 1080p monitor is a good compromise between immersion/quality/performance. Sent from my iPhone using Tapatalk

It's fine. You'll be able to run X-Plane on very high settings. Sent from my iPhone using Tapatalk

1. The bump is cause by the mesh. 2. a. Have you added to your scenery an airport boundary? b. You might have to edit the mesh.

I don't think that there is something like that available. Better ask to Gizmo Support forums for that.

Probably Cameron meant Gizmo runs only in 64-bit.

Search And Rescue mission in the central Aegean Sea, south of Mykonos.

With all the heat lately about "study sim", this puts everything to what is what. Not flicking few dummy switches, but real technical simulation. Leading Edge stuff! EDIT: Not ready for Christmas??? Who cares...

As I mentioned in my previous post, if you have the Gizmo plugin installed in your X-Plane installation...you are good to go. No need for anything else. For example if you have skymaxx you do have it. To clear things up a bit, what Gizmo does is translates your scripts written in lua to that kind of code that X-Plane understands, without the need you to code in c/c++ and compile. So, you ending up coding in much easier to understand programming language, save the file, press the reboot on Gizmo in X-Plane that run simultaneously, and your code is running, with all debugging informations in front of you! Ultra fast procedure which makes coding really fun! Specially for guys like me, who here and there forgot to put an "end" in a function! Gizmo syntax can be found here: http://gizmo64.com/Gizmo64_API.htm

SHJ, First of all I have no formal education in programming. I have though the curiosity and the patience to learn, try to understand sometimes things that are mind bending (when you don't have the formal education), and the persistence to try and fail until succeed. In brief, back in 2012, after learning a bit my way around in blender, I start developing an update for the XP9 Avanti to Avanti II. Very soon came to a problem. The landing light switch in Avanti II has 3 positions. OFF-TAXI-LDG. Now, I'm in a fully 3D cockpit... how I'm gonna do that? I asked as you did and got the same answers. Plugin! I said noway! But a guy offered to do that for me. He wrote a short script in SASL with a ton of comments. That was everything! I started to read and understand how this worked...ending up to release the aircraft with a total 14 scripts, 36 custom datarefs, with a fully simulated autopilot, custom draws on the PFD/MFD etc! Ok... i had to ask again few times, but about 95% was my own staff. I'm not saying all these to make me look...an amazing person, but to underline that is not the hardest thing in the world! Now, my suggestion is to start looking at lua, the programming language for Gizmo and SASL... or forgot SASL... look at Gizmo only since is the only one that is fully supported and most developer-friendly of the two. Oh, did I mentioned and more powerful too? It is! If you have one of X-Aviation products installed, then you are ready to start! Go here http://forums.x-pilot.com/forum/117-gizmo-development/ to read about tutorials, other members questions etc. To start playing with this go to and aircraft (like the KC-10 which is free from other plugins), and create (in the KC-10 folder) a folder named "scripts". Open a text editor (if you are using windows notepad++ is free and more that enough to start with), create a new empty file and save it inside the scripts folder as "init.lua". Go back to the text editor and paste this code: --Everything after the double dashes is a comment and will not affect the script.--Like keeping notes to know what everything does.--Programmers: I keep it as simple as possible to make it very ease to understand...Don't shout on me...but correct me if I'm wrong.airspeed = dref.getDataref("sim/flightmodel/position/indicated_airspeed") --We read the indicated airspeed from X-Plane and store it into "airspeed"lg_handle = dref.getDataref("sim/cockpit2/controls/gear_handle_down") -- Same here. We read the gear handle position from X-Plane and store it into "lg_handle" function main() -- From this point to the "end" of the bottom we do all our stuff! local as = dref.getFloat(airspeed) -- We store locally the value of "airspeed" to "as" to use it below if as > 160 then -- We are checking if the airspeed is above 160 kts, then... dref.setInt(lg_handle, 0) -- set the landing gear handle to 0, which means up, hense...gears up else -- in every case that airspeed is not bigger than 160 kts... means of course equal or less than 160 kts dref.setInt(lg_handle, 1) -- gear handle down -> gears down end -- end of that "if" paragraph! end --end of the functionNow save the file. Fire up X-Plane, load KC-10 and take off. Watch what will happened when the airspeed reaches 160 kts...Gears up! Slow below 160 kts. Gear down! Now the aircraft has an automatic system to deploy and retract the landings gears! Time for you to play now... Of course this is probably the simplest example, but enough for you to start crawling! Best Regards

I do not want to disappoint you, but X-Plane's default "systems" have a certain logic attached to them. If your needs dictate a different logic, then the use of a plugin is the only way to go. I've been there and I know. And by using a plugin, open a whole new world of possibilities.

To my best of my knowledge, Saab 340A is not properly equipped for the execution of that kind of approach. That's why there are other types of approaches available like: https://skyvector.com/files/tpp/1513/pdf/00545VGB.PDF In general, there are tables at Charts.pdf in the Manuals folder, on page 105 and 106 that gives you the altitude where you will start the descend, the distance to land with headwinds/tailwinds, even the fuel consumption. These tables assume that you are flying in you depart your cruising (or current) altitude in IAS HOLD mode and power levers to flight idle. That's the way that mostly this type of aircrafts meant to be flown.

Dear Pilots, Just a short update on the progress of our Chicago O’Hare Airport project. This project is #1 in our priority list. We are working really hard to give you the best possible scenery can be done, and we will not give or try to achieve any chronological target. Where we are today: - Mesh: We are in the progress of editing the mesh to give the airport some of its distinctive features, like the basins, taxiways A and B underpasses and more. But we have hit wall! Somewhere in the chain of the workflow, there is a link that creates as a final result small gaps on the mesh around the edited part. We are doing exhausting research to overcome this “wall” and continue, because without the final mesh ready, some things cannot progress. And leaving gaps on the mesh in a no-go situation. Our “mentality” is to do something right or not do it at all. - 3D Modelling: All the terminals are modelled and now we proceed on adding details on them. We also have modelled about the half of the rest buildings. There is still a lot to be done (that’s a HUGE airport, and one of the most complex in the world!). - Airport Layout: The airport layout will be as is today, meaning that we will include the recent delivered in traffic runway 10R/28L. And will be distinct that is a new runway! So 9 runways in total! Talking about complexity! Also we have requested from Laminar to add the new runway’s ILSs in a coming update, so when it we will be ready for release, the naivads will be in place too. If you don’t know those things come from X-Plane database and cannot be added/altered by scenery authors. Best Regards

Definitely! Sent from my iPhone using Tapatalk

Specially when you are alone in the cockpit and VATSIM controller gives you a different arrival than the planned one!

About GPS. It's a "dummy" one already in the cockpit (still you can click on the screen and get the popup - default behaviour thanks to Laminar!), mostly to check the placement and the visual interference. We've also tested the 530, but was covering almost all the middle front window! About CBs. Expect only the main items to be covered. You will not need to worry for the... lavatory lighting!

Thanks mate! Circuit breakers is not in my opinion the hardest think to simulate. That said, it does not mean that in every flight you have to trip CBs all the time! In contrary, you will barely see this happened. And we are not going to introduce random failures, rather failures as a logical consequence of what's happening. But, we want to have that factor in the pilots consideration, because that looked the life back then. Today, systems are way more reliable, so it's not that big factor. Cockpit color will be in accordance with livery. What the airline was using? For fictional liveries haven't been considered yet. Actually is already there! (the GPS) Sent from my iPhone using Tapatalk