chris k

Hi Guys, Actually - I was just thinking this exact same thing as I was fooling around with SMPv2 yesterday. The ability to [reset to factory defaults] would be appreciated, this way I don't have to remember whack knobs Ive turned, and where to put them 'back' once I've fiddled with them. +1 on this idea. Thats is all. - CK.

As mentioned by sundog, I confirm that this happens even in an XP10 "vanilla" beta install. I have such an installation setup for testing purposes against the "as-shipped" scenery, with no SkyMAXX or any other add-ons - this occurs from time to time with the betas too. - CK.

There were no effects used. That is a straight unedited screenshot.

http://www.x-plane.com/?article=x-plane-10-30-release-notes Scroll to the end

Whats "SceneryFX?" - I don't understand your question.

732.45 GB I have an entire 1 Tb HDD setup just for XP. Has 4 Copies of X-Plane: 1 "Demo" Install - Useful as a "Water World" for quick scenery testing (scenery reloads are very fast)1 "Full" install with lots of scenery, libraries, and pulgins for main use and scenery conflict testing1 "Vanilla" install with only X-Plane official files as distributed by Laminar as a benchmark1 X-Plane 9 Install for regression testing Plus all development Tools and relevant project files. (i.e. WED files, Raw untouched orthophoto PNGs, sketchup and COLLADA models, and the like) I use symbolic links all over the place to minimize file duplication as well, else this would probably be much larger than it is. - CK.

There was once a plane from Nantucket.....

Toronto and nope - not yet. Much work to do first.

I spend more on coffee in a week.... $25 is cheep. - CK.

It's actually the top metal Lids they're missing. The Socket is the same. Just it's slightly thinner die (vertically) as it has no integrated head spreader (IHS). i.e. the die is exposed not he top. Just don't tighten down the heatsink all the way and you'll be fine. Instancing *does* work on nVidia, but it's slower than non-instancing, so yeah - it's still broken. - CK.

If you want a second machine say for visuals- Try to score a pair of Xeon X5680 or X5690 CPUs on eBay and swap out the CPUs on your 4,1. There's some great tutorials out there on swapping the 4,1 dual socket processors.

The older (first gen) i7 / w3500 Xeon CPU is definitely the cause. A 2.2 Ghz with a 4.2GT/sec QPI bus is to blame. I replaced my CPU with a W3690 (3.46 Ghz @ 6.4GT/sec QPI) and popped in a GTX 670. It's acceptable now - but not stellar. I use it for all my development - since if our scenery runs well on my older-gen machine, it'll run even better on a reasonably modern system. -CK. Ps make sure you've downloaded the nVidia OSX "web drivers" from nVidias website. They bump up your card from PCIe 1.1 to PCIe 2.0 speeds.

Oh Wow! It looks like we have 2 people working on Toronto at the same time. This may be interesting - CK.

It has been a most productive Weekend: EDIT: forgot to add the Obligatory Night Shot: Cheers. CK.

- If you're planning on using a LOT of Orthophoto scenery, then yes, 4 Gb VRAM on the 760. - If you want to use stock scenery, or just dial down the texure res a bit with orthophotos, but have a 25% faster card, then go for the 770. Performance difference here: Hope this helps. FWIW - I use a 2 Gb VRAM GTX 670.. which is somewhere in between, and uses the same nVidia chip as the GTX 680/770 (GK104 chip) - and it's pretty awesome. I believe the 760 uses the same chip, just at lower performance. I don't think you could go wrong either way. - CK. p.s. there's been a few times I wish I had more VRAM when doing scenery development. Hard to have WED and XP10 open at the same time with a ton of orthophotos:

Most likely to "keep it simple" for the Steam Users. Holy Bejesus, have you seen the Forum/Discussion posts on Steam in the last 2 hours? I haven't seen this many A$$Hats at one time before in my life! - CK. Latest Review: "lolloll ok so i got it but what do i do it sucks no way to click tings off the window and cant access what does this do it sux!!" - Rating 0/5, Hours Played: 0.01

Unfortunately - That's actually a different object. 10.30b5 - Resources/default scenery/airport scenery/library.txt EXPORT lib/airport/Common_Elements/Fuel_Storage/Sing_Tank_Large.obj Common_Elements/Fuel_Storage/Lg_Fuel_Tank.obj EXPORT lib/airport/Common_Elements/Fuel_Storage/Sing_Tank_Medium.obj Common_Elements/Fuel_Storage/Med_Fuel_Tank.obj EXPORT lib/airport/Common_Elements/Fuel_Storage/Single_Tank_Large.obj Common_Elements/Fuel_Storage/Sing_Tank_Large.obj EXPORT lib/airport/Common_Elements/Fuel_Storage/Sing_Tank_Small.obj Common_Elements/Fuel_Storage/Sm_Fuel_Tank.obj 10.30b6 - Resources/default scenery/airport scenery/library.txt: EXPORT lib/airport/Common_Elements/Fuel_Storage/Sing_Tank_Medium.obj Common_Elements/Fuel_Storage/Med_Fuel_Tank.obj EXPORT lib/airport/Common_Elements/Fuel_Storage/Single_Tank_Large.obj Common_Elements/Fuel_Storage/Sing_Tank_Large.obj EXPORT lib/airport/Common_Elements/Fuel_Storage/Sing_Tank_Small.obj Common_Elements/Fuel_Storage/Sm_Fuel_Tank.obj If I change it as you suggest - then it'll actually show the wrong object..... i.e. that's not exactly a 'fix' - more of a work-around to show a different object in it's place. Ben has acknowledged this'll get fixed in Beta 7: ________________ From: Ben Supnik <xxx@xxxx.com> Subject: Re: Bug report: Missing EXPORT of lib/airport/Common_Elements/Fuel_Storage/Sing_Tank_Large.obj Date: 13 July 2014 12:25:44 pm AEST To: Chris K <xxx@isdg.com.au> This will be fixed soon in beta 7.

More work on Toronto: And testing YSSY stuff in 10.30:

Ensure youve installed it in the correct Hierarchy It should match something like this on your Disk: Should just be straight copy into /Custom Scenery/ from the zip - Are you on Linux, MacOSX, or Win7/8? - Can you post up the contents of your "X-Plane/Log.txt" here - CK.

FYI - Seems there's some LIBRARY directives not being exported correctly - which is resulting in some errors so far. "lib/airport/Common_Elements/Fuel_Storage/Sing_Tank_Large.obj" exists in 10.30b5 - Does not exist in 10.30b6 in Resources/default scenery/airport scenery/library.txt Basically some scenery will throw errors - and not much I can do......Bug Report Submitted to Ben. 0:06:01.920 E/SYS: +-------------------------------------------------------------------------------0:06:01.920 E/SYS: | Error loading the scenery package:0:06:01.920 E/SYS: | Custom Scenery/CYYZ Toronto Pearson (ISDG)/0:06:01.920 E/SYS: | The scenery may not look correct.0:06:01.920 E/SYS: | Please see the log.txt file for detailed error information.0:06:01.920 E/SYS: | (io_dsf.cpp:675)0:06:01.920 E/SYS: +-------------------------------------------------------------------------------0:06:01.920 E/SCN: Custom Scenery/CYYZ Toronto Pearson (ISDG)/Earth nav data/+40-080/+43-080.dsf:0:06:01.920 E/SCN: Unable to locate object: lib/airport/Common_Elements/Fuel_Storage/Sing_Tank_Large.obj- CK.

TrainSimulator does allow users to upload their own creations BUT: It's part of the "Steam Workshop" hooks. It's not part of the main game or existing pay ware DLC system. It's only for "free" files. There's no payment or DRM enforcement method for "true" 3rd party developers to sell an add on Product via Steam Workshop. It's nebulous as to "who owns" the workshop material. As per Ben R's post above - it appears that valve can exercise some kind of rights over your creation. If an end user wants to charge for his creation, They need to turn it into an official DLC by getting the original game developer to publish it.... Thus opening up a giant can if worms in terms if revenue and support. The Canadian Rockies DLC for TrainSimulator is a prime example of this. It wasn't developed by the game publisher at all... It was done by a 3rd party in isolation, but had to be published (and thus sold) as a DLC. All revenue goes to the original game developer directly - and not the company who actually developed the Add-on content.

http://eadt.eu