holimoli

Congratulations Stuge :=) thanks to all of you guys for the tournament. I really enjoyed it! Well done! Are you going to stream the 2v2 matches today? :)

"=","-" adjusts HDD zoom and your displayed range on the HUD (Bar on the left) simulationsly "rCtrl + =" and "rCtrl + -" sets your expected target range. You have to adjust the distance manually with "=" and "-". If you lock a bandit the range bar on the left will automatically adjust. Same as in the F15. Difference is that your radar cone is always the same in distance. You only adjust your systems how they display radar data and not the sensor itself. For example. If your range scale is set to 100 you will still see contacts further away at the top of the HUD.

Wrong. The expected target range does not affect how your targets get displayed on the HUD. Again: The radar cone is fixed in width, height and range. All your expected target range does is changing the amount of how much your radar cone is raised or lowered per elevation change. Fore example a higher expected range value will give u less change of the radar cone per one elevation click. So the expected range stands in relation with the elevation setting of your radar. To get back to the awacs calls. For example, if you get information about a bandit at 5000m and 30km away from and you are flying at 3000m then you can set your expected range to 30km and the elvation +2 and the antenna of your radar will be exactly pointed on the bandit. This does not mean that the bandit will be seen in the center of the HUD.. This dependes on your radar range settings displayed on the left of the HUD.

Perfect. That's nice! :thumbup:

a. correct. The radar cone is fixed. b. I think the intercept mission has an AWACS set. So you might see contacts received by the AWACS. c. ? ? ? Are you manpulatiing the radar at all? Like in elevation and azmiuth? d. ? ? ? No targets = no lock :P

Yeah, I thought about the same: If it's even possible that only certain ppl like admins or groups can use the F2/F5 view. I dont know much about DCS server/console stuff but I'm afraid it might not possible. :( I would stream If I could. Unfortenately I have pretty bad internet too... :cry::cry:

How can u justify publishing tacviews right after the matches but being against streaming? ;). Isn't this the same ? :P I think you can get much less information out of a stream which shows aircraft in F2/F5 view with a 3-5min delay than watching a tac-file. I'm not againt publishing tacviews during the tournament at all, I just want to have a fair tournament for all ppl. And IMO it's somehow unfair when ppl can't watch tracks of their opposite bracket opponents cuz they've got walk-overs. Anyway that's just my opinion :).

You are probably right. Just thought having one guy who spectates and streams it. This would be the right step to push such events more into the e-sports scene.= more support and more ppl I actually dislike publishing tacviews right after the matches. This might give certain ppl a possible advantage over others ( e.g. ppl who get walk-overs).

what about heaters, any changes ??

btw any chance we can watch the coming machtes via youtube/twitch streams ? :) Would be awesome.

I'll be there sat&sun.;)

yes, I dont have screenshots at hand... but have seen this a couple of times already..I have seen trees in the air too.;)

I thought about the same...like: What does the pilot use as reference for manipulating the radar and why is it like 6,3 up and 3,8 down. Anyway, I can't continue my tests atm since the ruler on F10 is bugged. Once that has been sorted I'll try to finish my tests :) P.s.: Sry for the late reply

in the F15 its even worse. And this is smthing since 1.5. It doesn't matter what I use. I do this. Go forward in the cockpit with (rshift+rctrl+*) then I zoom in (* or "Zoom View" or "Mouse Zoom View") and i go back in the cockpit (rshift+rctrl+/). If i do it the opposite way my HUD gets smaller. edit/update: I even deleted the freetrack files and did it with out freetrack. It's the same

The arrow on the B-E taxisign points in the wrong direction. Coordinates in the screenshots. Thanks!

Happens not all the time..but in certain places in clouds (seems to be more on the edge) the clouds are in front of the HUD filter and the HUD itself. See screenshots. Thanks.

no.. I think its bugged

Nickname: <51P>Holimoli Your profile at ED forum: http://forums.eagle.ru/member.php?u=115161 Chosen plane type: F-86F Country of residence: Austria Time: GMT+1 Language of communication: English Confirmation of familiarization with regulations of the tournament and the obligation to comply with them: Familiarized with regulations of this tournament, oblige myself to comply with them.

just go under your saved games/dcs open beta folder/config/settings.lua open it with a notepad and change the cockiptlanguage line.. seems they removed the drop down box.... options = { ["difficulty"] = { ["birds"] = 0, ["cockpitLanguage"] = "english", <- ["cockpitVisualRM"] = false, ["easyCommunication"] = true,

u can change the hud language in the options menu

yes, feels like the aircraft textures are sharper now.

check the pins of the joystick-throttle connector cable aswell. Maybe smthing is loose or twisted there. Especially check the small pins of the connector. Those are for the signals.

I see, yeah that makes no sense.:/ yep..still I'm gonna do some more tests to be precise as possible. Honestly the best would be if some of the mods could kindly ask one of the devs about the radar. :) :):music_whistling: Thanks though for your help and effort!

I think the pressure isn't set when u enter your aircraft. That's where the discrepancy comes from...Might be wrong though... I'dont have much experience with this. So basically u are getting the same values as I am..hmhmhm..So if the radar is 6,3°-3,7° it should look like this:

really interesting.yes.. Here is in detail what i did to get the 6,3° up. I began from the beginning. I put my contacts at 3 different altitudes again based on an assumption the the radar cone is either 10°,7° or 5° up in its initial position. I put myself at 2000m alt. I put again 3 contacts 40km ( It was a little bit more..like ~46km) away, heading towards me. The contacts had altitutdes of : -Contact1: 7053m (= tan(10°)*40000) -Contact2:6906m (=tan(7°)*40000) -Contact3: 5300m (=tan(5°)*40000) All 3 contacts had 500TAS I started the mission hit the active pause key and waited. So i have 3 contacts at 3 different altitude flying towards me. All I had to do is wait until one of those contact fades from the radar, then hit the pause key go into f10 measure the distance and read the alt. These are the results: Contact1(10°) : Is not visible at all... This means the radar doesn't look 10° up. Contact2(7°): The contacted faded @44240m from me. Since the radar does take 1-3 secs to update and myself needs like 0,3-0,5s to react. I did it twice and added some meters due to the radar update delay and took the average of it. 1st run: Contact2 fades@44240m, Contact3 fades@29670m 2nd run: Contact2 fades@44450m, Contact3 fades@29680m I took these values and added some "radar update delay", calculated the angles and took the average. 500TAS leads to 138,89m/s Contact2-1st run: 44240+(1*138,89), 44240+(2*138,89),44240+(3*138,89) Contact2-2nd run: 44450+(1*138,89), 44450+(2*138,89),44450+(3*138,89) Contact3-1st run: 29670+(1*138,89), 29670+(2*138,89),29670+(3*138,89) Contact3-2nd run: 29680+(1*138,89), 29680+(2*138,89),29680+(3*138,89) I calculate every angle with arctan((contact alt - my alt)/(contact distance)) For example..Contacts 1st run values: 0sec delay: arctan((6906-2000)/(44240)=6,33° 1sec delay: arctan((6906-2000)/(44240+138,89)= 6,31° 2sec delay: arctan((6906-2000)/(44240+2*138,89)=6,29° 3sec delay: arctan((6906-2000)/(44240+3*138,89)=6,26° and so on.... I couldn't find any mistake yet..so I assume the 6,3° is right..but again this value seems really odd to me and I'm gonna do some more tests... :)