Leaderboard

Доброго времени суток! Поздравляю всех вирпилов и любителей авиации с наступающим 23.02.12!!! К этому празднику я подготовил небольшей клип. Жаль что ютуб подпортил качество, в данный момент делаю клип с моделями СУшек 3GO а так же Combatace. Всем приятного просмотра и попутного ветра! ;)

One in twenty is enough when you throw a thousand rounds downrange. I assume you're familiar with how CBU's work? You might want to tell that to the F-15E that was shot down by AAA on 17 Jan 1991. We also lost an F-4 and an F-16 to AAA on 19 Jan and 27 Feb, respectively. An F-15E was shot down by an SA-2 on 19 Jan 1991, so ECM didn't save him - or three F-16's, an A-10 and an F-117 lost to radar guided SAMs since then.

OK I wish for a better insight of your virtual pilot's achievements. Let's see...with LOMAC and FC 1.1 we had an option to access more details of separate sorties. We could see date and time of each sortie as well as its duration in hh:mm format. We could se the airbase where we finally landed and plane we've flown during that mission. With FC2 logbook got redesinged changed but we can only access overall fight hours, kills, points, crashes, refuellings etc. I wish to have more data...for each mission I've flown. An option of saving debriefings would be great as well. Another cool thing to have would be exportable logbook so all fight hours logged as well as ranks and medals can be used with future DCS modules. For instance, I've bben playing simulators since I was a kid starting with Chuck Yeager Air Combat, A-10 Tank Killer, Microprose F-15, F-19, F-117, Jane's OAF, Jane's F-15Strike Fighter etc and finally in late '90 got attracted By Falcon 4.0 and Flanker. So back with LOMAC and Open Falcon I started using MS Excel to log my flight hours or the hours i've spent in front of my monitor with stick in my hand and results are somewhat astonishing: Open Falcon / Allied force - 620 hours LOMAC - 427 FC1.12 - 683 FC2.0 - 353 Ka-50 - 94 A-10C - 5 I wish could export and use same pilot profile since my first days of LOMAC. I'd be a president by now...

Right now, if you know what you're doing, you can blow through the startup extremely fast. We're at the point where every checklist has 'filler' features like checking the fuel gauge and oxygen gauge even though we all know there's no way either of those would be bad (I don't even think it's possible for the fuel quantity indicator to fail in the sim). So, I suggest we enable the preflight BIT... you know, the thing where all the crap flashes on the HUD... well, it's supposed to be interactive. You're supposed to center flight controls, arm EAC, enable SAS, arm it again, it tests GCAS, etc. It's a vital step no pilot would ever skip because it tests the vital systems that you trust to stop you from smashing in to the ground. With that in mind, I suggest that, maybe for DCS: A-10C 2, we enable these BITs, and even allow them to fail if performed wrong or if the system actually is bad - right now the GCAS BIT passes just fine even if your RALT is turned off, and presumably if it was completely broken too. Then again, I'm in to the whole random failures and maintenance aspect of these aircraft which seems to be an unusually unpopular stance...

Hello JG_14 You asked in your PM how i got my PVI-800 and UV-26 displays working on my second monitor. Please find attached copies of the files that i use:- In your BS2 installation look in these locations :- E:\DCS Black Shark 2\Scripts\Aircrafts\Ka-50\Cockpit\EKRAN\Indicator E:\DCS Black Shark 2\Scripts\Aircrafts\Ka-50\Cockpit\UV_26 E:\DCS Black Shark 2\Scripts\Aircrafts\Ka-50\Cockpit\PVI Back up your original copies of the... Ekran init.lua PVI init.lua UV 26 init.lua Then replace them with my files.... The viewportHandling.lua will disable your SHkval, UV-26 and PVI-800 "in cockpit" displays, but still allows exporting to your second monitor. It is located here:- E:\DCS Black Shark 2\Scripts\Aircrafts\_Common\Cockpit Then it's a case of adjusting your monitorconfig file to position them in the correct location, Hope that helps Regards Gunner.... BS2KA50.lua Ekran_init.lua PVI_init.lua UV_26_init.lua ViewportHandling.lua

Мне название как-то непонравилось )))

Это что празднование 23 февраля повлияло на эти хотелки? :)

More and Impressive news from Bohemia for Arma3. Those screenshots look amazing. If the gameplay is even a little bit better than it is now i will be in love again. And not to forget all the amazing things the community will be able to do with all the new features like swiming underwater, changing uniform, Physix and animations. Just wow. Quote from Bohemia: This will be awesome. We can even provide more community feedback in a pre-Alpha. No more lots of bugs at initial release, cause we will be able to find them and report them early. :) :) And the most importend feature for Arma 3.

Yep, missed that the first time through. Nonetheless, the canopy itself never actually fogged over like the accident aircraft's did, and it didn't exactly occur at a critical phase of flight, either. Edit: I didn't see a link to the actual report, so here it is: http://www.militarytimes.com/static/projects/pages/022112_f16_report_executive_summary.pdf

Тогда уж и кондуктора посадите чтобы билеты продавал. Кстати вот вам и новый DCS LEGENDS!

На yuplay.ru скидка 50% - 250 рубликов. А обновление с первой версии на вторую вообще 125 :)

Руки прочь от троллейбуса!

Ich bin nicht mehr ganz auf dem Laufenden, was den Status des Handbuchs angeht, ich werde aber mal beim Team anfragen.

I just hope mankind still inhabit the planet Earth at the time that happens.

Thanks Pittbull for putting together your results! @Gunnergolly This is not my config tool !! The culprit lies in your "destRect line of [Head1] Have a look at this again: This is your line that causes that the exports appear at the x0/y0 coordinate of Head1: destRect=0,0,1154,1080 but it must look like this to shift it to the right, where you want it to appear: destRect=767,0,1154,1080. But this doesn't will help to higher your FPS much. By only "cutting out" and teleport this part of the overall DCS render your card still will have to render te 1920x2130 beforehand ! You have to optimize first your DCS render to reduce the workload for the card - just because you are not "seeing" this black render at your monitor - it is still in the backbuffer of your GPU !! Have a look at this to realize what your card have to do - before SoftTH moves this part for the second monitor: Have a look at your current render: So you first have to edit your "MonitorSetup".lua and options.lua to get rid of this big chunk of unused render-area. This is how a optimized DCS-render would look in your case: And Than you have to rewrite a SoftTHconfig. I know that creating this new "MonitorSetup".lua can be tricky. Tip: Have a pencil and paper near you and use a painting-program with a pixel-ruler >>> - because you need a Desktop-area of 2754x1050 to check the edits - so first arrange your monitors side by side and start DCS windowed to be able to see what you are doing. So it's not a trial and error any more! Once all is in place - like on the picture above - than utilize SoftTh. I hope I pushed you now into the right direction and I wish you a happy editing! And keep in mind >>> SoftTH is donation-ware! ;) I suggest 1$ for each frame you gained using SoftTH instead of running DCS windowed. (Much,much cheaper than buying a new GPU!)

Тролейбус был бы полезен, если за его поражение отнимали бы кучу очков или вообще - провал компании...

Frostiken, this is what could have been.. Also... Watch carefully... (if you're busy, just start at 3:05) It's important for the convergence of perception and reality. I say these things in humor and with patient, good will.. :smilewink:

The grammar police are on their way.

It appears ED to be in monopoly position ,but It's not. People have already decided next is F18, but there's seven-g with more than 80% work has been finished.I think if ED cannot put out first , ED will ultimately pay a heavy price.

Flying into the sunset... And a lucky shot with the camera...

:megalol:

I am not sure I see that, I mean if they were all about the money they would pump stuff out alot faster than this and probably not near the quality they have been producing. If I was going to be scared or worried about anything is that maybe they are having issues acquiring enough info to model another top fighter, and that is the hold up on an announcement, but that is all just random thoughts not based in any facts what so ever :)

I know :) ufff Navy aircrafts foreva :]

If that was directed at me, none of those setups are mine. I use a Samsung 46" LCD, and input lag is not an issue for me (although I've only used it with DCS). Can't imagine it would be an issue at all, but I could be wrong.

That was easy! Culprit lies in your config.SoftTHconfig: First: Set zClear to 0! - this will prevent a shader bug with DCS. >>>Strange water texture overlaping bug... or something and you don't have the enableVBQuirk=1 line in the [debug] section! this also is a DCS specific Fix! (First post in this thread - written in red! I told this already two times to you!-don't you listen? ) Than: Keep in mind that SoftTH can only use the resolution your Monitor is set in windows properties when using the "destRect=" function. And you have a res of 1024x768 available on monitor 2. But you "teleport" () the 700x700 of the left MFCDs outside the space of your second monitor... The destect function doesn't start counting at x0/y0 of your overall resolution. -this does the sourceRect line already - The destRect= starts counting in the x0/y0 of your target monitor. So: the destRect for line for [head 1] should look like this to bring the L-MFCD back inside your available res . destRect=0,0,700,700 Read the line like this: Take pixelinfo determined by "sourceRect" and place it on the monitor with the ID [Head1]=Win-Mon-2. Start drawing at x0, y0 on [Head 1] and in size width:700px, height:700px. I hope that was clear enough..! Can be complicated at the start- as you have to think in several layers . But this is a very powerful function that let you render at the smallest possible resolution - and than spread the pixelinfo on different monitors. - look at the example of BadCrC and his cockpit again - to fully realizes what is possible with this. >>>http://forums.eagle.ru/showthread.php?p=1349597#post1349597 BIG EDIT: And as I said before: I would recommend to do it like this (see spoiler) - so you are able to use the HDR function without the sun-glare miss aliment >>>HDR Sun Glare Missalignment Your card should be powerful enough for this. option.lua: options = { ["difficulty"] = { ["padlock"] = true, ["easyRadar"] = false, ["miniHUD"] = false, ["birds"] = 0, ["optionsView"] = "optview_all", ["permitCrash"] = true, ["immortal"] = false, ["easyCommunication"] = true, ["map"] = true, ["radio"] = false, ["labels"] = true, ["tips"] = true, ["cockpitLanguage"] = "english", ["units"] = "imperial", ["easyFlight"] = false, ["altTrimmingMethod"] = false, ["externalViews"] = true, ["iconsTheme"] = "nato", ["fuel"] = false, ["weapons"] = false, ["setGlobal"] = true, ["geffect"] = "realistic", }, -- end of ["difficulty"] ["graphics"] = { ["shadowTree"] = false, ["sync"] = false, ["multiMonitorSetup"] = "1camera", ["color"] = "32", ["heatBlr"] = 0, ["scenes"] = "high", ["water"] = 2, ["fullScreen"] = true, ["visibRange"] = "High", ["aspect"] = 1.342657342657343, ["haze"] = 1, ["shadows"] = 2, ["TranspSSAA"] = true, ["cockpitShadows"] = false, ["width"] = 1920, ["effects"] = 3, ["MSAA"] = 3, ["height"] = 1430, ["HDR"] = 0, ["civTraffic"] = "", ["lights"] = 2, ["clutterMaxDistance"] = 0, ["textures"] = 2, ["treesVisibility"] = 6000, }, -- end of ["graphics"] ["views"] = { ["cockpit"] = { ["mirrors"] = false, ["reflections"] = false, ["russianHud"] = false, ["avionics"] = 0, }, -- end of ["cockpit"] }, -- end of ["views"] ["sound"] = { ["world"] = 0, ["radioSpeech"] = true, ["cockpit"] = 0, ["volume"] = 0, ["headphones"] = 0, ["music"] = -12, ["subtitles"] = true, ["gui"] = 0, }, -- end of ["sound"] ["miscellaneous"] = { ["headmove"] = false, ["force_feedback_enabled"] = true, ["f5_nearest_ac"] = true, ["f11_free_camera"] = true, ["synchronize_controls"] = false, ["accidental_failures"] = false, ["f10_awacs"] = true, ["Coordinate_Display"] = "Lat Long", }, -- end of ["miscellaneous"] } -- end of options config.SoftTHconfig: [main] renderResolution=1920x1430 nonlocalFormat=RGB16D keepComposition=1 smoothing=0 debugD3D=0 zClear=0 vsync=0 tripleBuffer=0 screenshotFormat=jpg dllPathD3D9=auto dllPathDXGI=auto dllPathD3D11=auto [overrides] forceResolution=0 antialiasing=0 processAffinity=1 FOVForceHorizontal=0 FOVForceVertical=0 [debug] compatibleIB=0 compatibleTex=0 compatibleVB=0 enableVBQuirk=1 [head_primary] ; borderA=0 ; borderL=0 sourceRect=0,0,1920,1080 screenMode=1920x1080 [head_1] ; borderA=0 ; borderL=0 devID=1 sourceRect=0,1080,350,350 destRect=0,0,700,700 transportResolution=350x350 transportMethod=auto noSync=0 fpsLimit=0 [head_2] ; borderA=0 ; borderL=0 devID=2 sourceRect=350,1080,350,350 destRect=350,0,700,700 transportResolution=350x350 transportMethod=auto noSync=0 fpsLimit=0LMFCD+Camera+RMFCD.lua I did set your MFCDs to 350x350 - don't worry - this is absolute sufficient! -this will cut the needed bandwidth for the MFCDs to a quarter. Proof that the MFCDs will be still usable at 350px: Same picture as above - but now resized to 700px vertical. This is same what SoftTH will do : But I advise not to go below 300px - or the smallest font will get very fuzzy and also symbols at the TAD ! _ = function(p) return p; end; name = _('MFCD Softh'); Description = 'Left MFCD on the left monitor,Right MFCD on the right and camera on the center' Viewports = { Center = { x = 0; y = 0; width = 1920; height = 1430; viewDx = 0; viewDy = 0.3; -- Fine tune this to move your center-viewpoint up/down aspect = 1.342657342657343; } } LEFT_MFCD = { x = 0; -- don't touch this if it doesn't fit at first -- start! do changes only in the y = 1080; -- destrect line of softTH for positioning!! width = 350; height = 350; } RIGHT_MFCD = { x = 350; -- don't touch this if it doesn't fit at first -- start! do canges only in the y = 1080; -- destrect line of softTH for positioning!! width = 350; height = 350; } Gui = { x = 0; y = 0; width = 1920; height = 1080; } UIMainView = Gui- You will still have to fine tune the position of you MFCDs in destrect line- as I don't know how your Helios-profile looks. but now you can use a overall res of 1920x1430, you will have 350x350 MFCDs that will be resized to 700x700 by softh. And you can finally use the HRD without sun-glare missaliment! And for the sake of clarity : a visualisation what SoftTH is doing in this case. And as a last step you should fixate your FPS to something like 30-40 FPS in the Eagle Dynamics\DCS A-10C\Config\graphics.cfg line #393 >> "MaxFPS = " Do this to prevent you card from a overhead render that can cause stutters and distract the "smoothness" - because your FPS can jump between 70 to 15 within a half second. Make first some tests where your average FPS are - but a value around 30 is a good choice. This is much better as using the SoftTH "smoothing" function as DCS has it already build in!