So another update in 10.10b5 and which way do we go? – Well forward of course.
10.10b3 was a bit of a dog, 10.10b4 was a step in the right direction – but 10.10b5 is certainly really quite to very good.
I feel at the very top end I have lost just a little of my framerate performance, not that much and finally you certainly don’t feel you are on a cliff anymore and that you are going to crash “out of memory” at any minute, and I would say it it is smooooth, really smooth.
But here is the good feeling
I have enlarged my numbers so you can see the frame rate 28.14 – In the Dash, and in the clouds?…. getta out of here!
(my computer specs are noted at the bottom of the post)
And like I mentioned it was all very smooth.
I am still having an issue with using the HDR “on” as well, simply brilliant at night – but I am still not convinced in the daytime.
HDR “off” is quite good
The gamma with HDR “on” is still very noticably far brighter and the aircraft is far more (very) jaggy around all areas, to which I would say it feels like a drop (stop down) in texture render settings – here it is set to “High”
I will note is this really cheating?…by going down a step in render texture settings to make it perform better with HDR “on” to match the HDR “off” frame rates… hummm, I wonder.
Close up with HDR “off” the detail is simply first-rate and this is in just in the standard “High” setting.
This is all with a speed busting 80 frames as well, the detail of the leading edge is simply perfect.
Yes I am running Mountain Lion so I will take that into the equation, but I feel that 10.10b5 is still a step forward.
The line between HDR “on” and “off” in some (many) areas is now very small so in many cases you can leave it switched on
A nice sunset image shows the great light and the reflection of colours on the x737′s wing, this image is with HDR “off” and with the “visibility” (weather) setting about half way, it all works so very nicely thank you.
Traffic and trains seems to be far smoother as well to which I will relate to the HDR tweaks, this is in Kansas (Setting) .
But the train signaling still needs a little work…
The new feature in 10.105b is “Quicklook” QL for setting your views in a 3d cockpit.
And very good it is as well.
Press your usual “3d cockpit” (or 3d_cockpit_cmnd_look) view and then set your new view via your usual keys by Rotating left, right, up, and
down or Zoom in and out – then when you have the view you want just press “CONTROL” and a number on your keyboard (or Keypad) from 1 to 10.
Then go back and then press the same number and you are zoomed straight to that view.
It was great to set the view exactly where you want it, and then to come straight back to the same view on a single push of a button.
To get this view usually means a lot of scrolling around the Q400 cockpit.
The Overhead light switches were very hard to get to as well.
The great feature about all this is you are in control, you set the place you want and not what someone else thinks you want – and still then you can always scroll and adjust to right or left if you need to.
And if you like that view better then just save it (CONTROL-number) – simple as that.
Then you can get creative!
I always love the passenger view.
Settings are for that Aircraft and you have to start from scratch with any new file.
Drawbacks, I found a few.
If you have a key assigned to a number (key) then the assigned key over-rides the “view” save.
You can assign any key by using the keys “setup” in the “Buttons: Basic tab of the
Joystick & Equipment” menu window – which gives you more freedom of setting it up where you want them.
I questioned the differences between quick_look_0 and quick_look_0_mem.
And Chris (Serio) noted this :
“The “_mems” are the assignment keys. So they should almost always be the same as the quick_look keys but with a modifier. So by default 0-9 for quick_look and CONTROL+0-9 for _mems.”
Remember there are two versions of view, you could say one is “inside” which is the 3d (Cockpit) and “Outside” which is the general views.
You toggle between them by using the 3d Cockpit view, once inside the 3d view you can move around inside the aircraft setting your different views, If you move outside the aircraft to take the same 3d views of the say the front of the Q400 or the x737 then that view will also be stored.
But I found that on some aircraft (Challenger 300) that you can’t move outside the boundaries of the 3d cockpit?, inside was fine…but there was no way I could move outside and probably related to the update in 10.05rc of “(ATTR_solid_wall now works again.) ”
On the Q400 I had no issues, so it will depend on what file you are using if you can move outside with every aircraft?
If you save a view with the general view it will save the view but in the “moving spot” position.
So if you turn then the camera will stay in the same place but it will note the new angle of the view.
Unlike the 3d views which go straight back to the same visual viewpoint.
All views are stored in a _prefs.txt in your aircraft folder and it looks like this.
If you need to move it then just copy and paste the _pref.txt file to the new aircraft folder like in the instances of an update, say with the x737 and that way you don’t have to input them all again from scratch
Overall the new “Quicklook” feature is excellent, I love it, It is very easy to use and highly adjustable to use on the fly, but I will have to totally rearrange my key setup to make the best use of it.
Also noted in 10.10b5 is the changes to the manipulator that you use to twist knobs and tune equipment around the 3d cockpit. (mostly the Autopilot)
It is now a new pixel-based manipulator lets you define drags that work horizontally or vertically, with scaling. This manipulator is now intended to make knobs draggable.
This Item was brought to the table at Laminar by Javier Rollon. And mainly because the default B747-600 was so impossible to adjust in any direction, I find most working ideas in these manipulators work fine – but some are very distracting if your workload is high (say on landing).
The developer will have to update their products to take advantage of the feature so it won’t be noticeable until a few updates hit the shelves.
I need to run a few very long simulations to really test the update, but my feeling is that we are getting close to dropping out of the beta stage soon, 10.10b5 is certainly very sturdy and smooth.
To note a feature that is coming soon in 10.10b6 is the “flashlight” that was noted yesterday by Tom Kyler.
Which proves the genius of X-Plane, come up with an idea and it is quickly a new feature – It will be great for those cold, dark mornings….brrr.
As they say around here “have a good one”
- 2.66 Ghz Intel Core i5 iMac 27”
- 6 Gb 1067 Mhz DDR3
- ATI Radeon HD 4850 512mb
- Mac OS Mountain Lion 10.8
- X-Plane 10 Global