-
Posts
1,840 -
Joined
-
Last visited
-
Days Won
57
Content Type
Profiles
Forums
Latest X-Plane & Community News
Events
Downloads
Store
Everything posted by chris k
-
The Hampster is ALWAYS right. World domination is next.
-
Starting to get all the stuff finally aligned to the ortho. (Yes, those are all 3D objects, including the vehicles and walls) - CK.
-
??? 10.20's are more "complete" than 10.11 is, for sure. Describe your problems (in the HELP forum) and we'll go through them one by one as to why you'd make that conclusion about the 10.20 run... assuming you want to try out 10.20-64bit and the new Autogen.
-
Erm, just because someone doesn't have a payware airport doesn't make XP crash or anything. Half your users will still be on XP9 too, with a completely different terrain elevation mesh. I supppose you would allow them, but deny others? The whole point is "come with what you got" Anyways most of the payware sceneries have equivalent freeware as well (klax ksfo cyvr kjfk kord eham etc...) so I don't think that'd be an issue.
-
Load order is important. (The "Demo Terrain" will cease any further loading of scenery for the KSEA area). Stick mine first. I don't have any weird exclusions in mine... so it should just lay down the orthos, suppress some silly-placed Autogen, and let the regular KSEA Demo airport come through. You can probably just deactivate the KSEA Demo Terrain if you have a full XP10 install. (Don't need the terrain since it's also included in the full DVDs install) Play with it a bit till you get it right =) Should be straightforward to play with the order (theres only 3 combinations possible anyways heh)
-
File Name: X-Plane 10 Compatibility Library for X-Plane 9 File Submitter: chris k File Submitted: 31 Dec 2012 File Category: Plugins and Utilities X-Plane 10 Compatibility Library for X-Plane 9 Dec 31, 2012 - Version 1.0 By: "Chris K" and the ISDG Group Happy New year to All X-Plane 9 users.! Here is a gift for you..... From Us. ___________________________________________________________ WHAT DOES THIS DO: This Library allows X-Plane 9 users to load X-Plane 10 Scenery files (with caveats, see below) ___________________________________________________________ BACKGROUND: Here's something I thought about a few weeks ago; in terms of providing SOME kind of compatibility between XP10 sceneries and XP9 sceneries. I am primarily developing for XP10, and don't want to have to do 'parallel development' in terms of providing backwards compatibility to XP9. (I wish to work on one project, not two). Instead of myself creating a "kludged" (Nerfed?) version of sceneries for XP9 (which I had done in the past to provide XP9 users something), instead I decided once-and-for-all to fix the problem at it's root. ___________________________________________________________ HOW DOES THIS WORK: This "shim" library file inserts blank objects, facades, forests, etc. where they exist in the new XP10 Library system. This is similar in nature to how the OpensceneryX "placeholder" library works, but this time we apply it to every single XP10 library object we could find. This tricks XP9 into loading most XP10 scenery; as the library paths now resolve. The list is accurate as of XP10.20 beta 10. I have tested this on my own scenery packages, and it works. ___________________________________________________________ CAVEATS / WHAT DOES NOT WORK: You will not see any XP10 objects (hangars, gates, lights, etc.) You will not see any XP10 facades (terminals are a big one) You will not see any XP10 forests You cannot use large (4096x4096) textures: If a scenery uses a draped polygon of greater than 2048 resolution on any side, XP9 will crash out. This is a known XP9 limitation; as it was only in XP10 that texture sizes were allowed to be increased. You cannot use XP10-style facades If a scenery uses an XP10 style 'custom' facade (FACADE 1000), XP9 will try to still load the facade, and proceed to crash out. I have tried the EDPORT_BACKUP trick, but it's a no go, since the file can actually be found (and still tries to use it, despite the version string). You cannot use XP10-style Airport Layouts. XP9 Will Ignore them. But! You *CAN* cheat!... and try to change the first few lines of the apt.dat file in a custom scenery to say "850" instead of "1000". I have tested this on YPAD for example, and it worked, despite there being custom ATC information encoded in it. ___________________________________________________________ HOW TO EXTEND: Got an object I missed? or a new facade showed up from somewhere? Edit the library.txt file; find the "virtual" path that the scenery is using, and add the appropriate line to the library.txt file. Have a look at the text file - it's pretty self explanatory the 3 fields you need =) Also, let me know if you found something. I'll include it in the master DB I have here. ___________________________________________________________ WARNING: This Library and associated files are provided "as is". No Warranty; No suitability of fitness for any purpose; May not even work. Insert standard "Boiler Plate" Here. ___________________________________________________________ © 2012 Chris K and the ISDG Group Click here to download this file
-
Version 1.0
247 downloads
X-Plane 10 Compatibility Library for X-Plane 9 Dec 31, 2012 - Version 1.0 By: "Chris K" and the ISDG Group Happy New year to All X-Plane 9 users.! Here is a gift for you..... From Us. ___________________________________________________________ WHAT DOES THIS DO: This Library allows X-Plane 9 users to load X-Plane 10 Scenery files (with caveats, see below) ___________________________________________________________ BACKGROUND: Here's something I thought about a few weeks ago; in terms of providing SOME kind of compatibility between XP10 sceneries and XP9 sceneries. I am primarily developing for XP10, and don't want to have to do 'parallel development' in terms of providing backwards compatibility to XP9. (I wish to work on one project, not two). Instead of myself creating a "kludged" (Nerfed?) version of sceneries for XP9 (which I had done in the past to provide XP9 users something), instead I decided once-and-for-all to fix the problem at it's root. ___________________________________________________________ HOW DOES THIS WORK: This "shim" library file inserts blank objects, facades, forests, etc. where they exist in the new XP10 Library system. This is similar in nature to how the OpensceneryX "placeholder" library works, but this time we apply it to every single XP10 library object we could find. This tricks XP9 into loading most XP10 scenery; as the library paths now resolve. The list is accurate as of XP10.20 beta 10. I have tested this on my own scenery packages, and it works. ___________________________________________________________ CAVEATS / WHAT DOES NOT WORK: You will not see any XP10 objects (hangars, gates, lights, etc.) You will not see any XP10 facades (terminals are a big one) You will not see any XP10 forests You cannot use large (4096x4096) textures: If a scenery uses a draped polygon of greater than 2048 resolution on any side, XP9 will crash out. This is a known XP9 limitation; as it was only in XP10 that texture sizes were allowed to be increased. You cannot use XP10-style facades If a scenery uses an XP10 style 'custom' facade (FACADE 1000), XP9 will try to still load the facade, and proceed to crash out. I have tried the EDPORT_BACKUP trick, but it's a no go, since the file can actually be found (and still tries to use it, despite the version string). You cannot use XP10-style Airport Layouts. XP9 Will Ignore them. But! You *CAN* cheat!... and try to change the first few lines of the apt.dat file in a custom scenery to say "850" instead of "1000". I have tested this on YPAD for example, and it worked, despite there being custom ATC information encoded in it. ___________________________________________________________ HOW TO EXTEND: Got an object I missed? or a new facade showed up from somewhere? Edit the library.txt file; find the "virtual" path that the scenery is using, and add the appropriate line to the library.txt file. Have a look at the text file - it's pretty self explanatory the 3 fields you need =) Also, let me know if you found something. I'll include it in the master DB I have here. ___________________________________________________________ WARNING: This Library and associated files are provided "as is". No Warranty; No suitability of fitness for any purpose; May not even work. Insert standard "Boiler Plate" Here. ___________________________________________________________ © 2012 Chris K and the ISDG Group -
Hi Keith We were planning on doing FACT South Africa as the first one... I think that's well clear of SOCAL? =) - Ck.
-
No Worries Keith, and thanks for the note. Basically, it was just for a "free for all - come as you are - with VOIP" I think Erik is after. (not any True ATC); and I agree, you don't want to dilute the branding youve built. Again, VATSIM is my suggestion. I'm sure the controllers in any area are happy to receive a gaggle of birds in their nest for a fly-in. - CK.
-
You forgot to stencil "Copyright" all over those images. I will steal them now. - CK.
-
VATSIM (No Voice unless there's a controller, text works) IVAO (No Voice at all, text works) Xflightserver (No Voice at all, text works) NetFlight (No Voice at all) Take your pick. You do realize if you choose Xflight or Netflight, mot of us don't have accounts on those..... Hence, VATSIM would be my #1 choice due to the integrated VoIP capabilities. (Hard to type when both hands are on the controls, but I have a nice PTT voice key on my throttle I use all the time) You could even contact the FSS associated with Cape Town and arrange an ATC for voice services if you'd like... Im sure they'd appreciate the traffic. - CK.
-
PilotEdge is the best that they come. Others are free, yes, but (1) lack the integrated voice unless there is a controller on, or (2) have no voice capability at all. - CK.
-
Hrm, can Keith or lwilliams pipe in here? I think PE may be the better way to go vs Xflightserver. (as it's a far superior platform both in terms of speed, update fidelity, and audio quality) Any "free for all days" planned?
-
The Scenery errors are very simple to explain: Custom Scenery package "KFLL" is attempting to load at art asset form the X-Plane 10 Scenery Library. Oops. X-Plane 9. That'd do it.
-
Oops! Almost forgot the most important thing in this scene - The Coffee!!! ^^ Totally Canadian, eh? Model by Skyflyer! - EDIT: Ignore the ground texture - it's purposely "low rez" in this area. (since you're not likely to be at street-height in your airplane along Derry road..... unless you're Andrzej)
-
High and Dry Over RWY Zero Five.
-
Ensure your HSI selector is set to GPS, (not NAV1/NAV2) EDIT: On second reading, you need to note that the"flight plan" you file is completely separate to how you setup your aircraft. Theres not any"auto magic copying" from a Fight Plan to your GPS in your airplane (just like real world). Filing a Flight Plan does not mean you've tuned your radios/setup the Garmin, etc =) No Magic allowed =)
-
Update to XP9.70 http://www.x-plane.com/downloads/older/
-
Vertigo?
-
I like Pie. Discuss.. =)
-
10.20 should be out of Beta soon. We use many of the new art assets found in the new builds to flush out the scenery. No Plans for Brissy or Mexico yet.
-
.. and remember. Whomever makes a 64-bit plugin for online multiplayer first... wins. =)
-
Bad news: Instancing still Broken. Good News: Check out these results: 10.8.2 = Latest nVidia WebDrivers: 304.00.05f0210.8.3 = New Apple-Shipping Drivers: 304.10.65b07______________________________________________________Test 10.8.2 10.8.3 Increase1024x7681 fps=39.20 fps=45.21 15.3%2 fps=27.07 fps=31.29 15.5%3 fps=21.65 fps=25.31 16.9%4 fps=22.45 fps=26.81 19.4%5 fps=46.13 fps=53.88 16.8%______________________________________________________1920x12001 fps=35.57 fps=42.71 20.0%2 fps=20.50 fps=23.95 16.8%3 fps=15.61 fps=18.28 17.1%4 fps=16.32 fps=18.93 15.9%5 fps=46.55 fps=54.27 16.5%______________________________________________________ Yep - Definite Improvement - Not Anywhere near Win7x64 yet on certain tests - but creeping pretty close! A significant showing. - CK.