Jump to content

efis007

Members
  • Content Count

    616
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

877 Excellent

About efis007

  • Rank
    Member
  • Birthday 04/18/1963

Profile Information

  • Gender
    Male
  • Interests
    Sky Environment observation and analysis

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

Recent Profile Visitors

2,932 profile views
  1. From the site... https://www.x-plane.com/2024/02/whats-new-in-x-plane-12-1-0-oh-boy/ Physics-based Camera – shipping in 12.1.0 or another upcoming release This new in-cockpit view option moves the camera based on the acceleration of the aircraft In real life, the pilot viewpoint is not locked at single point because their necks are not locked in a single position. Thus the pilot’s view moves as a damped spring. Oh my God, now we also missed the "physics-based camera" !!! πŸ€¦β€β™‚οΈπŸ€’ This craze for "excess realism" is causing damage after damage. I hope this new camera feature in 12.1 can be disabled in the options menu. πŸ™ I have already tried to fly with these "physics cameras" (XP-realistic plugin, example), but the experience was very short, I immediately deactivated them because it is impossible to control the avionics of the plane. In fact, the "vibrating camera" doesn't just make the head move, but it makes the entire image on the screen move, therefore it is no longer stabilized. Let's remember this word: stabilized. When I tried to control the avionics with XP-realistic I could no longer keep the mouse pointer on the knobs and buttons of the cockpit because the mouse - due to the wobbling of the display - continually loses its position on the avionics instruments! 😣 If the image on the screen constantly wobbles (and consequently the mouse also wobbles) how can I center the knobs and buttons correctly?! Furthermore, the concept expressed by Austin according to which in reality our head is similar to a spring, and consequently the image on the screen MUST wobble and vibrate, is total nonsense. πŸ€¦β€β™‚οΈ In the real world the head moves but our brain always carries out constant and powerful image stabilization which allows us to see the world as still and stable as possible! In the real world I don't see the outside world "wobbling" as I walk down the street. In the real world I don't see the outside world "wobbling" while I drive the car. The head may move as Austin claims (which is true), but in the real world the perceived visual effect is NOT remotely similar to the "XP-realistic" plugin or any other crazy "sickening shaky camera" effect. Understand LR? Ok the "realism". But there is a limit between common sense and madness. Please stop this madness of imitating the behavior of cameras !!! Our eyes and brain are not cameras and do not behave like cameras !!! Austin wants to implement a nauseating new camera effect? And so be it. The important thing is that that effect (far from realistic!) can be optioned and deactivated from the menu, the user must have the ability to turn it On or Off. ------------------------------------------ Before finishing I will also add a further note. Xplane12 wants to imitate cameras. But has anyone on the LR team ever noticed that modern photography-filmography is increasingly oriented towards image stabilization? Today almost all modern cameras are stabilized, they make use of gimbal stabilizers, processors with stabilizing algorithms, optics with stabilizing mechanics, and any other type of device designed specifically to AVOID shaky representations like those that Austin would like to offer us on XP 12.1. That old-fashioned way of making the image shake on the display is something that should be avoided, it resembles the old black and white films of the LumiΓ¨re brothers from 1895 who used old non-stabilised cameras (and the films shown in theaters were all shaky because it couldn't be done otherwise). But today we are no longer in 1895. Today the world has changed. Today, professional aeronautical videos are not produced by making shaky shots, but rather by making shots that are as clean and stabilized as possible because (1) they are more beautiful, (2) the customer doesn't have to feel nauseous when watching the video. So here's the Austin paradox. If Austin in XP12.1 wants to imitate modern cameras (i.e. stabilized) he must paradoxically leave the images still and stable exactly as they are now in v12.0. ------------ However, as I said before, if Austin wants to put the sickening camera in v12.1... so be it. As long as it is optional, and never the default.
  2. It was my favorite plane in XP10, really nice and graphically excellent. πŸ‘
  3. In the meantime, I thank you for the time you dedicate to our questions and I hope you do a good job with LR. πŸ‘ I want to ask you a question. You mentioned β€œautoexposure.” In all the experiments I have conducted so far the "eyes autoexposure function" has always damage my graphics (the sky became white and overexposed, and the panels even darker and underexposed). We both know that XP12 has big problems with tonemapper, lighting, shadows too black, etc... we discussed this at length in another topic. But in addition to these problems I had highlighted ((showing curves and histogram graphs) how the "eyes autoexposure function" contributed to further damaging the graphics by burning the overall exposure of the image. For example that horrible blinding white sky is only generated due to the "eyes autoexposure function" ! By removing that function the sky becomes blue, just as I see it every day in reality. πŸ‘ And so I did: with the ART controls, I removed that function, and had a clear graphic improvement. Finally the skies are no longer white, the sunsets are no longer pale, and the cockpits are less dark when I keep a frontal half panel/sky shot. Fantastic. After seeing how much the graphics improve without the "eyes autoexposure function" I am perplexed to turn that function back to "ON". So I was wondering, and I'm asking you only out of my own curiosity: - In the next XP12 versions is it absolutely necessary to implement the "burnt graphics function" again ? And if YES, why? πŸ€”
  4. Wow, absolute incredible πŸ‘
  5. It's nice to see the old legendary simulators that kept us fellowship for years.
  6. I'm not using any cloud tweaks/mods, all scenery and clouds are default. The only trick I use is this, I'll share it for anyone who wants to use it. https://mega.nz/file/g5oTXRgB#6uhL59gbgsdhTXXyDz3IWHn7PjbnIIfxKdt8XJ6Q8YE The package consists of three elements. (1) Lua scripts completely eliminate the "self-exposed camera effect" (which causes unnaturally white skies and pale sunsets). Furthermore, the script softens the tonemapper and makes the shadows inside the cockpit less black. This temporary measure is not 100% effective, but it allows for more visible and illuminated cockpits while we await the next v12.1. The script also eliminates the star wars black rain effect. (2) Another lua script (optional) controls the LOD and framerate stability. (3) Finally, the "blufx" plugin performs real-time light/color correction without loss of framerate or stability. This plugin simply needs to be installed and that's it, I have already calibrated it to have good color correction.
  7. After fixing anti-aliasing, dark panels, and color correction, my satisfaction with the new XP12 is increasing. Today the simulator amazed me, I was doing a normal scheduled flight between Quito (SEQM) and Jorg (SPJC), and during the route I was surrounded by many cloud formations and thunderstorms (I was flying in real weather). Well... XP12 recreated fantastic clouds! ... I had never seen clouds so well shaped and above all varied in design. Thunderstorms for example. I expected to see "square thunderstorms" (we know that Xp12 sometimes creates ugly, square clouds). None of this was generated. The clouds were all beautiful, the storms had a very convincing "anvil design", and they were beautiful even when viewed far away on the horizon. Yes ... I really liked Xp12 today and wanted to share these captured images with you. Observe how beautiful the distant formations are! When I landed I moved the clock forward, and XP12 gave me the final surprise: a beautiful moon that dazzles the storm clouds. What a day! 😊
  8. I quote myself to correct my mistake. I did further testing and noticed that the "old Xp11 script" also works with Xp12. Probably in the first tests I manipulated too many art controls, and therefore the script did not seem to work at all. Instead it works. πŸ‘ The antialiasing trick suggested by Franz007 also works. Nice Shot. πŸ‘ And a very old XP10 freeware plugin even works, I used it to do light/color correction without using Reshade (which often crashes the sim). With these temporary tricks my Xp12.0.8 has now improved (I show some photos below). I'm sure that v12.1 will definitely be better... but in the meantime I'm enjoying this souped-up v12.0. πŸ™‚
  9. I had already discovered the solution proposed by the Org forum 4 years ago with XP11. https://forums.x-plane.org/index.php?/forums/topic/122225-very-dark-cockpits/&page=2#comment-2094117 The script trick is 100% identical to that of the year 2020, and consists of removing all the shadows or lightening them so that they are less black. Unfortunately this trick (which worked very well in XP11) does not work effectively with XP12. Due to the new lighting system the XP12 cockpits do not improve with that script, they do not become at all as bright as in XP11. Personally I'm no longer using that trick with Xp12, it doesn't work well and generates graphical bugs on the edges (the frames) of the cockpit instruments. πŸ€·β€β™‚οΈ Currently the only script lines I'm using in Xp12 are these: set( "sim/private/controls/autoexposure/gain_hi", 0) set( "sim/private/controls/autoexposure/gain_lo", 0) set( "sim/private/controls/autoexposure/null_hi", 0) set( "sim/private/controls/autoexposure/null_lo", 0) set( "sim/private/controls/tonemap/blend", 0) set( "sim/private/controls/rain/kill_3d_rain", 1) -The first 4 lines block the "blinded camera effect". Finally no more white overexposed skies! No more destroyed sunsets! No more cockpits that turn light and dark as you move your mouse! No more cameras inserted into eyeballs! πŸ™Œ -The fifth line slightly increases the overall lighting tonemap contrast. πŸŒ„ -The last line block the "squid black ink rain effect". πŸ™ These six scripts lines do not solve the most serious problems of XP12 (antialiasing bug, tonemapper bug, etc etc). For the fixing of those defects we have to wait v12.1.
  10. Cirrus SR22 wing textures are painted dirty by default. The realweather or rain is irrelevant.
  11. @jcomm Changing the nvidia sharpness parameter does not cause "wall clouds". πŸ˜‰ My Xp12 is all default, no scripts or nvidia modifications. Yesterday while I was flying over Thailand I saw some famous XP12 bugs in latest 12.0.8 RC3: - Wall clouds. - Squid ink rain. - Very bad sawtooth antialiasing (the anti-aliasing degrades considerably when the plane is photographed in front of the wall clouds). - The omnipresent dark panel. All these bugs depend exclusively on XP12, not on Nvidia driver changes, and will hopefully be fixed ( 🀞 ) in the upcoming 12.1 release.
Γ—
Γ—
  • Create New...