slip-stream

Too true. I can't believe they stuck Scotland on the back burner to release unfinished Ireland. What was that all about. I'm fed up with waiting for the scotland collection now.

I'll second that. Rob, are you surprised at the Scot S release date being put back? I'm not.

Scotland South has been delayed until late Dec. No mention on the forum though.

Me too mogget. They are terrible at customer service. Ask for an update and it gets deleted. Yes Anthony. England and Wales is at 1.2mpp and Ireland. Scotland will be at 60, including Orkney, Shetland isles (already released) the last update was for scotland s to be ready any day now. Version 3 of England and Wales has a number of cities at 60cmpp.

Fantastic news. Thank you. Sorry for being off topic. Would love to see some beta screenies if you get the chance.

No. There is an addon called treescapes though. This scenery does not require autogen. Looks better without.

http://www.playhorizon.co.uk/forums/viewtopic.php?f=10&t=4354Check out my screenshots Anthony.

No apology reqd. Just frequent updates on your forums please. Looking forward to the eventual release. I have the virtavia version which has a cracking VC. Terrible rotor effects though.

Shame they haven't put as much effort into their CH47 project. According to milviz forums it was nearly complete over a year ago.

Could you please elaborate on the highmemfix?

Agreed Anthony, at that height. However, at 60cmpp you get the 4000ft clarity at 1000ft. Don't believe me? Buy the orkney isles.

I'm just patiently waiting, along with Chris, for Scotland South. @ 60cmpp it's going to be incredible. Their forum is a joke though, most posts just get deleted for some reason. As for the scenery appearing 2D, false. Looks exactly as it does in real life.

Most of those skidmarks are mine. I've been flying since FS1 so that would account for most of em. Sorry. Lol.

Ah. Yes it was the rotor effects. Thanks anyway.

Is there a way to swap these effects? Basically I have two versions of the same helo and the one with the most realistic VC has a not so good rotor effect, whereas the other is perfect. Is it possible to replace the bad with the good version?

I have a single 50 incher in 3D and a touchscreen similar to the video. I am going to buy 2 more 50 incher's and have them in a box shape and use those for my direct left and right views.

Compatible with TIR?

Me too Bill. I was thinking along the lines of this company who opened their doors to the public yesterday to fly the 777.http://flightdecksolutions.blogspot.com/

Thanks Bill. So I could purchase a licensed copy and then charge people to fly my simulator, right?

What does the Retail License @ $499.00 allow you to do then?

Your best option is to SLI 2 GTX 480's or buy the latest Geforce GTX 590 and set resolution to 5760/1080 with bezel correction. Far better than any matrox setup. There is no reason to run multi monitor setups in windowed mode. As long as you resize and get everything exactly how you want it and then save in win mode you can then revert back to full screen mode. The key thing to remember is to always exit FSX in win mode.

Thanks again. I searched the SDK and found nothing relating to size. It all makes sense now. Tom, the above proved to be correct. I now have all 3 gauges present in the correct location. (autopilot is slightly over to the left.)The only issue for me now is to find a way of converting the VC collimated HUD so that it also shows up in the 2D view. You will see from the attached image that I have the outside view rendered in 3D, but with a 2D HUD. The VC HUD renders in 3D. [Vcockpit08] references the VC HUD.//F-35A Panel configuration file[Window Titles]Window00=Main panelWindow01=HMDWindow02=Default Radio StackWindow03=Default GPSVIEW_FORWARD_DIR=-1.000, 0.000, 0.000//--------------------------------------------------------[Window00]Background_color=0,0,0 visible=1ident=MAIN_PANELalpha_blend=0.95position=8window_size= 1.000, 1.000size_mm=1024,1024 // Uncomment one of the lines below depending on your "WideViewAspect" setting in your fsx.CFG file.gauge00=F-35_HUD_VC!F-35_HUD_VC, 317, 211, 388, 691 // <--- F-35 2D HUD, conformal at zoom 0.9, aspect ratio 16:9 and WideViewAspect=False//gauge00=F-35_HUD_VC!F-35_HUD_VC, 330, 230, 364, 647 // <--- F-35 2D HUD, conformal at zoom 1.5, aspect ratio 16:9 and WideViewAspect=True//--------------------------------------------------------[Window01]Background_color=0,0,0 visible=1ident=MAIN_PANELalpha_blend=0.90position=5window_size= 1.000, 1.000size_mm=1024,1024 gauge00=F35!F35HMD, 0, 0, 1024, 1024 //--------------------------------------------------------// Default FSX Radio stack[Window02]BACKGROUND_COLOR=2,2,2size_mm=156,308position=8visible=0ident=RADIO_STACK_PANELzorder=3gauge00=Bendix_King_Radio!Bendix-King Radio Audio, 0, 0,156,31gauge01=Bendix_King_Radio!Bendix-King Radio Nav-Comm 1, 0, 29,156,59gauge02=Bendix_King_Radio!Bendix-King Radio Nav-Comm 2, 0, 86,156,59gauge03=Bendix_King_Radio!Bendix-King Radio ADF, 0,142,156,41gauge04=Bendix_King_Radio!Bendix-King Radio DME, 0,180,156,41gauge05=Bendix_King_Radio!Bendix-King Radio Xpndr, 0,217,156,49gauge06=Bendix_King_Radio!Bendix-King Radio AP, 0,262,156,48windowsize_ratio=1.000window_pos=0.756,0.358window_size=0.243,0.641//--------------------------------------------------------//DEFAULT FSX GPS//--------------------------------------------------------[Window03]Background_color=0,0,0 size_mm=456,378position=8visible=0ident=GPS_PANELwindow_size= 0.500no_luminous=1gauge00=fs9gps!gps_500, 0,0//--------------------------------------------------------[Window04]BACKGROUND_COLOR=2,2,2size_mm=1024,602position=7visible=1ident=12000gauge00=f35!autopilot, 0,10,512,90gauge01=f35!mfd1, 0,90,512,512gauge02=f35!mfd2, 512,90,512,512//--------------------------------------------------------[Vcockpit01]Background_color=0,0,0 size_mm=1024,1024visible=1pixel_size=512,512texture=$F351gauge00=f35!pfd, 10,100,1024,1050//--------------------------------------------------------[Vcockpit02]Background_color=0,0,0 size_mm=1024,512visible=1pixel_size=2048,1024texture=$F35MFD1gauge01=f35!mfd1, 0,0,1024,512//--------------------------------------------------------[Vcockpit03]Background_color=0,0,0 size_mm=1024,512visible=1pixel_size=2048,1024texture=$F35MFD2gauge01=f35!mfd2, 0,0,1024,512//--------------------------------------------------------Day=255,255,255Night=223,255,255Luminous=246,115,119//--------------------------------------------------------[Vcockpit06]Background_color=0,0,0 size_mm=1024,1024visible=1pixel_size=1024,1024texture=$F353gauge00=f35!autopilot, 0,10,512,90gauge01=F35!flightdata, 0, 934, 425, 90gauge02=f35!mfdhsi3, 15,140,200,200gauge03=F35!MFDcontrol,406,941,143,76gauge04=F35!MFDSwap,555, 941,159,76//--------------------------------------------------------[Vcockpit07]Background_color=0,0,0 size_mm=128,128visible=1pixel_size=128,128texture=$F354gauge00=f35!HMDToggle, 0,10,512,90//--------------------------------------------------------[Vcockpit08]Background_color=0,0,0 size_mm=1024,1024visible=1pixel_size=1024,1024texture=$HMD3d2gauge00=F-35_HUD_VC!F-35_HUD_VC, 222, 267, 549, 549 //// <--- F-35 VC HUD//--------------------------------------------------------[Default View]X=0Y=0SIZE_X=8192SIZE_Y=8192

Hi Bjorn, it's a Viseo 200T. Really happy with it. I'm using it for my F-35 Avionics display. Image is work in progress.

Roger that Bill, fully understood, now. Thanks.May I ask the difference between 'pixel size' and 'size mm'? gauge00=F-35_HUD_VC!F-35_HUD_VC, 222, 267, 549, 549 //// <--- F-35 VC HUD

Ok,, but why then do the coordinates match up exactly in the VC? That's why I assumed that no size and location editing was required.Thank's anyway Tom, Ed. appreciated.