chris k

Sorry - it'll be a No to v9 for now as Im using 4k x 4k textures (XP10.10 or better support those now). I can cut them into 4 tiles @ 2048x2048 if I feel up to it down the road... now that you mention it, yeah I should do that... Make Happy Happy Joy Joy for those v9 users like Mike =) - CK.

Some Misc Shots of whats going on in Santa's Workshop this month: - CK.

Charlie did a reasonably good Wellington - and Janwender did a back-port of Robin H's Auckland from the XPJets-team, much to the chagrin of Dhruv =) There's some older small-GA-field stuff done by RoyalOak as well (NZFF, Milford Sound, etc) kicking around. The majors are done though pretty nicely (NZAA, NZWN, NZCH, NZQN). - CK.

Sorry to hear you're having "missing object" and "apt.dat" error. ( can you elaborate on these?)

Wow! Thats lookin' Awesome guys!! Well done! - CK.

Huh? There's only EVER 2 conditions which makes WED crash: (From my own experience only...), and the crashes are predictable and repeatable: 1. You run out of Memory. Same problem that X-Plane 32 has. Easily done when zooming way out and you have orthophotos loaded. 2. You Export a Bezier Curve on a POL. Other that that - I have never experienced any kind of "random" crash at all. WED has been Rock Solid for every one of my projects since January. (aka once you know what contributes directly to the only 2 reasons it crashes - if you simply avoid them, then I can use WED for hours and days and weeks without a single crash). Heh. - Ck.

POLs cannot have bezier curves, Known issue. - CK.

Yep - Basically this is what you want in term of a direction to take: CPU: Quad Core i7 / Ivy Bridge / Around 3Ghz-ish GPU: nVidia GTX 680 with min 2 Gb of VRAM RAM: 8 Gb DDR3 at some reasonable speed (1333/1666) Everything else is just case/power supply/hdd/lights/plastic to hold it together. You could probably build a system simmilar to this for $1000-$1500 depending on the source of the parts. i.e. $769 for a GX680? You can get the 2 Gb version for $600-ish $AUD here in Chatswood or Crows Nest in Sydney - CK.

And the resulting URL you found it as was......? - CK.

1. You shouldn't cut holes in a POL - I cant think of any applicaiton where youd need to - without resorting to using other 'tricks' to achieve the same effect (i.e. Pol on POL, or using a layer-group). You *CAN* add additional verticies in a POL - but you must be VERY VERY aware of the OpenGL S/T Parameters you need to fix in order to have the Gfx card project it properly. Texture squished in 1 area? 2. Check the "S" and "T" Parameters on your verticies on your POL. Bottom Left= 0,0, Top Right =1,1 Do this by selecting one corner at a time.. and look at the element inspector on the right hand side. - CK.

Very Nice indeed! Gotta get me some of that =)

Good luck man! Stick to it - it becomes addicting after a while! Looking forward to your first release! - CK.

Use a Flight Simulator.?

Whatever you do - Don't say "Edit" and "DDS" in the same sentence....They don't belong together.! It's like saying "I still dont know what kind of jack hammer I should use to resurface the concrete sidewalk"; Basically, you don't "Edit" a fully dried, cured, and formed concrete sidewalk. You replace it with new wet concrete instead. - CK.

Note: you can keep BOTH the PNG and DDS files in the same directory. X-Plane 10 Automatically chooses the correct one depending on the user's [X] Compress Texture Settings. You also don't need to edit the "TEXTURE xxxxx.PNG" line in a POL file or any OBJ object. X-Plane simply ignores the file extension and searches for a .DDS (then PNG then BMP etc..) automatically. read: http://developer.x-plane.com/2012/11/dds-and-v10-what-does-it-do/ http://developer.x-plane.com/2012/01/dds-revisited-in-x-plane-10/ - CK.

Egads! How should I say this: "Youre doing it wrong". You are not supposed to edit DDS files! http://developer.x-plane.com/2012/01/do-not-use-dds-as-an-editing-format/ Think of DDS as the "End Result" of your work. Do all your work in PNG, PSD, other formats,etc. Once you're 100% done, then convert/process your imagery into DDS (and remove the PNG files from your distribution .ZIP file). Think about it like the music Industry (back in the CD days). Music editors don't do their work in 2-track 16 bit 44Khz (i.e. CD-quality). They do it on 24-track 32-bit quality at 60Khz. Once the track is COMPLETE, then they "downsample" and "package up" the music onto a CD. Or even better, the Music industry doesn't work in MP3 as their format. That's just the end-product (as it's a lossy distribution format, just like DDS is). XGrinder. Does all the X-Plane specific Gamma correction for you: http://developer.x-plane.com/tools/xptools/ - Just drag-and-drop the PNG images onto the Xgringer Window and Voila. DDS files appear in the same directory. Very Very easy. - CK.

Nice Anti-Aliasing...

START by using OE. OE is easier for the first time user (I believe)... and will allow you to add those statics quickly without having to learn much about the X-Plane scenery system. It has an easy and intuitive interface, good for learning, and shows you what youre doing in 3D "as you do it". WED is the "serious powerhouse" once you get the initial hang of how the scenery system works. WED's big advantage is the "offline editing" - meaning that you don't generate the final scene until you want to, and you an enable/disable portions of the scenery at-will (by hiding objects you don't want shown) and regenerating the DSF on the fly without deleting the object. You can also do mass copies, searches, search-and-replacements, and object alignments/naming in batches. You can even import existing DSF/Sceneries into it from other scenery packs - Most powerful. You can then re-enable something later on (hence you don't have to complete DELETE something in the scenery just to see what it looks like), and then have to re-add the object Like you do in OE. Very powerful for testing. Also, as the scenery file for WED is just a text file, you can easily hand it around to other developers as a complete project file. This is how our team does it - a master WED file in an online database that we all have access to (Dropbox), which we take turns editing our potion of. We can freely make changes and generate our own local sceneries "at will". This is much harder to do when you're mucking around directly with the "DSF" (final scene file in X-Plane format). Easier to do version control and do "diffs". Plus, if it ever "messes up", the WED project (being just a text file) is easily repairable. - CK.

Start dropping static acft in there.

BeachMAXX flor the shoreline and SkyMAXX for the water - CK.

Ewps. Sorry - Forgot that from the other thread. oh no! XP9 - why? =) Once 10.20 64 bit is stable (and the 3rd parties really start ramping up utlities/plugins), I have a sneaky suspicion that Xp9 is about to be left in the dust by the new year. - CK. BTW - 10.20 as well is FAR FAR faster rendering than any previous 10.x version. I can even now run HDR mode fullscreen with a ton of objects and orthophoto scenery - on a LOWLY 5770 ATi card anywhere between 20 and 30 FPS. Rock on baby!

Have you looked at the "DRAPED" option for your objects? http://developer.x-plane.com/2010/10/draped-object-geometry-in-x-plane-10/ and specifically: http://developer.x-plane.com/2011/04/draping-part-1-z-thrash/ http://developer.x-plane.com/2011/04/draping-part-2-draping-a-polygon/ This may fix any Z-buffering sillyness between a POL ortho and the object (I believe) - CK

Are you testing in 10.11 or 10.20? There's a reason. Certain Facades are broken in 10.20