Weltensegler

OK so I got the indicator backgrounds scripted and tested and put them in the Mod section for the next one that uses this kind of monitor arrangement. --> http://forums.eagle.ru/showthread.php?t=92461 They came for a price, my girlfriend is mad at me bc I talk only in lua to here now...and out-comment her all the time :D So now I will fly one evening before I start doing the performance tests and the summary. I actually haven't sit in the cockpit even since the monitors were horizontal and the sides weren't mounted! :)

Go for it! :) There is nothing better than switching in game screens and indicators off and putting mouse and keyboard away...and just fly

Hello Gentlemen I wrote some lines to create Backgrounds for exported indicators which are useful if you have to render them on top of your camera views for any reasons. Either bc your layout has 3 main screens with outta ones in portrait mode and your front panel in between or bc you like to have the instruments fix on your main screen for some reasons. It simply creates a black polygon in the cockpit and lays the indicator on top. So far I couldn't see any fps drop but why would there be since its just a polygon :) Just in case I pushed the polygon into the front panel so it is invisible anyways but still gets exported as static BG for your indicator. So far I did only the two most common front panel indicators for the A10C: RWR and CMSC. They do not all work the same way or with the same code bc they work in different scales and with different lua references etc. And since my time is limited and I don't even know if anyone is interested I suggest you test these two and just post here if you have the wish for another one. I'll try to take care of it then. For CMSC backup&replace: For RWR (AN_ALR69V) backup&replace: Consider the AN_ALR69V_init as export ready as well. To change size of polygon for RWR you need to update the coordinates of vertices for MAIN, BIT and COMMON equally! see comments in lua files I might write some master function for that sometime but on the other hand this is something you set one time only anyways. Not everybody feels comfortable with editing lua. So let me know in case you have any problems or questions. Have fun! AN_ALR69V_BG.zip CMSC_BG.zip

I use the 23" acer for my right (and switchable to left-) panel. (see cockpit link in signature) So far very good and reliable. You wanna put the bottom of the screen to the outside since the optimal angle for monitors is in general made to view slightly from above and in NVIDIA settings I toned down the gamma for it a bit to compensate for the lifted brightness of my personal viewing angle...but that depends on the angle you build it in. The photos don't represent the look very well since the angle is different when you sit and the phone camera doesn't have a good exposure either. Front panel is a 24" ELO touch...can't recommend that one. Its very heavy and deep.

I believe so too. Just human JTACs cant.

:) http://www.autoblog.com/2012/07/24/ford-unveils-red-tails-edition-mustang-gt-w-video/

Can't do it, Mr. Camel. Reading this thread on a phone while walking. Don't think I would have guessed the FOV that high on a screen either, more used to lens values. ;) Well then same you effort for the video, cptmoose

It almost looks too fishy for just a wide fov in the pic. Can you do a short video recording of zooming in and out and turning ur head? Just to make sure

It shouldn't be too strong though! Its actually pretty subtle.

:thumbup:Nice job! That looks very convenient!

:) wrong number please dial again, hehe But thanx for ur good intentions

I admit this was only a code sample to hook a script writer that might drop by and not a proper layout of the problem :) Well this code comes into the cmsc_page. lua not the monitor lua. Not at computer atm but in case you wanna try you can put it right over the the first "TXT" block after the local variables. Watch out the vertices of the mesh are in METER scale in case you wanna adjust to your own layout! And if you don't have the Z value in initial position at -1 then the polygon will actually stick in you ingame cockpit unless you prevent that by killing its render purpose. But no its unfortunately not that simple. I can have it in the cmsc and big enough to cover the rwr and at the same time have the rwr below the cmsc in the monitor.lua and it still gets covered. It must have to do with the way the rwr is coded bc I can fully control created polygons in level and depth in the cmsc but the rwr gets always covered or if I try to give the an_alr69v_page.lua an own mesh it just doesn't show up anymore...neither the indicator itself nor the mesh :) So I am trying to understand whats special about it if its parenting or radius/diameter code that works in a different scale. If so can I SetScale=(meters) or will then the whole indicator break? I need to spend some more nights with it. Never perfectly focused then but that's the time have left :)

Oh yes! Always planed peter. At the end there will be a summary and I am close but I'm not done yet! When I get my sripting to work and frames remain acceptable I will break it down for you guys! Little bit more patience so I can guarantee for the whole package :)

Well I don't change the procedure compared to when it works. Also sometimes they answer for start up but not for taxi etc. ...I don't know maybe they have a weak bladder and run to the restroom all the time. If you got taxi permission and roll on the runway they give you permission without that you asked for that's true but do they give taxi permission if you don't ask for it? Not sure...would have to try.

Yes I believe I wrote that in my boring text between the images :) The front panel is a 24" elo touch (would look for a lighter one if I were you) and the side panel is an 23" acer touch (I believe it was a T231H) I overclocked the 680 4GB ftw now very slightly to gain another 10fps. Now I get about 46fps in first instant mission which keeps me save in each scenario ground and most cities) when limiting them to 30fps.

Yeah my bad. I didn't get not lost in the "disable disabling" thing again :) its late here, sorry I believe disabling can give you more performance other than you use Helios then opposite is the case.

Stunning and beautiful work Sir! respect!

You will have the most amazing pit of all, Sir! On a second thought..get your thread outta here! That is aircraft restoration...not cockpit building! :D great job!:thumbup:

Insane! :thumbup: ...makes me want to start over again with my pit

nice setup, mate!! Yes softTH will also take care of your horizon issue!

nice work! looks awesome!:thumbup:

yes I have that since A10C beta in at least 80% of cases I have to do things before ATC answers me :) request start up? ..silence...I start up.."clear for start up request taxi...silence...I start rolling..."you are cleared for taxi I just got used to do it while I'm asking :D

I hope it rather gets fixed instead of a sticky for a workaround because its not a workaround for everyone. Some of us depend on Aero for their setups!

UPDATE - screens and right panel/hull Dirty stitching and my phone camera couldn't hold the exposure but you get the idea. Two 3/4 shots: If there is anyone that is good in lua scripting and you would have a minute for me, please PM me! :helpsmilie: I started scripting black polygons into the cockpit and behind the instruments since I have the sim also running in the upper half of the front panel and have no fps impact yet. But I do have trouble writing the same as a back layer for the RWR. It is extremely bitchy and doesn't accept and own BG-Mesh nor any of such from other instruments reaching over. This one of my working approaches for the CMSC. :geek: In this case it is using the CMSC's origin and also covering the AN_ALR69V but unfortunately its literally COVERING it. I tried writing it as a function tried to reference it from the definition files but I can't get it to work with the AN_ALR69V code. Maybe I have to define a different scale or set another origin within that lua. I have some theories but I'm missing parts of the puzzle. So if anyone is an experienced lua scripter here please gimme a hand! :helpsmilie:

Majesty Duckling! What an honor! :) Thank you! Always admired your metal frame work!