Doum76

Well seems it ain't a bug after all. :) https://forums.eagle.ru/showthread.php?t=214819

Yep changed that when Axis came along and how i figured that out in the CH Control Panel. ;) I was mainly flying the Huey since i got the pedals, so i didn'T really paid much attention to Wheel Breaks until i got the Hornet, wish i'd found the Axis while i was flying the Harrier, if it was implemented.

Thanks, never thought going into the controllers section for this not a bug thing:)

As you said then, structure or something stationary big enough? Just wanted to explore this, since most of the time i always used CCIP with eye contact.

Exactly :)

Yep that's what i do, was jsut wondering an alternative, it's easy for stand alone things, or building, but with VR, sometimes spot an isolated target not standing alone in the middle of a desert, is not easy. Guess i was doing th right way, was jsut curious to know if it was possible. No matter what, you need to do a recon pass to taly the target witht he diamond then going in with CCIP after that, at least, you'll get craters as reference :) Until we get TGP available.

Thanks to you too :)

Hey giys, i do have a stupid question here, are we able to use a waypoint set as designate target on the HSI but in CCIP rather than Auto/CCRP, no matter what i put on my Program it goes Auto as i designate as target... I'm wondering because to practice Waypoint UFC entering, i take a target Lat/Long coord on f12 menu, create a waypoint with it and, since UFC and HSI are not displaying the same Lat/Long, it covnerts and end up in an offset, which is a bit annoying as Auto bomb drop, so i simply wanna use it as designate target to spot on my HUD the target's area, but going in CCIP with visual cue adjusment for the offset created, if not i got to go in one shot, spot the target's area, un-designate waypoint as target and go in CCIP by remembering where the target was... Thanks

Oh right.. i reported my bug but forgot to mention yours, i'll edit my post. :)

Was wondering why i didn't get the new introduced CTEI / Perpendicular offset /abeam distance to course line. I use most of the time my HSI on left DDI, and it was hidden all this time, i guess masked where warnigns should appear, even though there is none, more likely a masking/alpha issue (not sure how it'S called in 3D, but you know the thing like alphas in Photoshop :))? As you can see in my screen shot, fine on right DDI, but on left DDI, only bottom of text shows a something is masking most of the text... Also, as JOJOZ mentioned in my other post, we wounder if there should be a negative and positive indication as to wether you're on right or left of the Course Line, we don't know if it's a bug but is this value supposed to be negative to the RIGHT and positive to the LEFT of course, it's not the case here, the value is always positive in the right or the left of course...

There we go, found the issue why i was not able to see it. It's as i thought, it's hidden on left DDI where i use the HSI mainly, but because i presume, alpha's or how even it's called is masking text where the warnings should appear for overlaping text even though no text are there, while on DDI it shows correctly as no warnings on that DDI.

I cannot answer you as with the Vive, since i went Oculus a fe wmonths ago, the main reason was, because i tried it, but mostly with the research i'Ve made, Oculus came out a few times as handling better in low frame rate condition and lower end system as i am having, so with my old i7-2600k stock, no OC, 16g ram, ECGA GTX 1070sc 8gb and SSD, depends on situation but it goes from 25 FPS- 45 FPS with lots of stuff on high settings (most of the time FPS drops a bit on carrier if i drop in static objets, if no objets, specialy no static F/A-18C lot 20, it's close to 45, of course, no mirrors and terrain shadow as flat. I'm sure with a 1080ti versus me you'll do way much better.

Dunno what i'm doing wrong, i'll retry it today, but wasn't showing... EDIT: i jsut tried and what is weird is, i do have something over it, looks like some info wants to show, but all i see is sorta small like on what should be the bottom lines of the letters/numbers, as if something is hidding the info... weird.. screenshot i made was in VR so quality is bad to show... i'll redo one later. One test i'll do is setting thwe HSI on right DDI, fow now i most of the time set it on left DDI, so maybe there's an alpha issue masking from the warnings text that overlap that part even though no warnings are there.... as the second lines og warnings gets to that spot....

Weird then if they implemented it, maybe only they find out tit was on some C models but not maybe the one they were looking it at that time.. i dunno, but weir di do not get it... you get it simply by entering a Tacan frq, then activate Tacan it in the HSI and it shows as default?

Same here, got mine a few months ago, and even with the lack of resolution we got on present VR headset, i simly not interested to fly on monitor, even when i force load non VR to du stuff in mission or stuff, i find it so much boring and the way too sharp details on my monitor, reminds me that wearing glasses, VR makes me see thing more like i am used to versus Supoer-Bionic super detailed world as monitors does. In otehr words, i can'T trade anymore Immersion, in world point of view for more resolution whle looking at my window and turning my head 1 degrees to mimick in sim 90 degress, love to force my shoulders 90 degrees or so to look 90 degree or so in sim :) I now realised my head/neck is not as flexible as it was in my younger days.

I can lend you my little cousin to kick your butt under your chair as you taxi or land to fix it until you find a solution, he can be really annoying sometimes. :P

Might not be your case, but.... I see from your signature's spec you are using CH Pro Pedals, are you using Toe Breaks for the wheel breaks? I was before and realised the issue you have was the one i had, i had Toe Break set to the keybinding from DCS (U i think), without any deadzone etc.. so as i landedand had my foot on the pedals, i didn'T realised i was slightly pressing the breaks, so the cable was pulling a bit back but not it's entire pull back cuz i was breaking without noticing it, so wasn't able to break out the tension on the cable.... might not be your issue, ut if set as it, simply pump the break when this happens and take your foot out of the pedals... on my side since i set up toe breake to axis and with a curve on the toe break, it doesn't happens anymore.

You're welcome, tried to answer from what i know.

It depends, can be fast, can take long, all depends on how it goes, sometime they might wait a few updates done on Beta, then run a bigger patch on Released to combine them all.... As they did with 2.5.2 on Released Version... If Disc Space is not an issue for you, you can always has the option to install both, so you has best of both world. That's what i did. So when they update something on Beta that screw up something, i can turn around and go in Released version until it's fixed.

You won't be able to, as you can see, both list are different, one has most of my bookmarked servers, while the other version only has one of my bookmarked server in it.

That i can'T say, if all patches makes versions uncompatible or when it's minor patches it stil can be compatible, if any patches makes a difference, then chances if you updated your Beta today that you can't connect with them as they are on the same version Beta was pre-today's patch. One way to easy know is, i can load my REleased version, see the server list i see and open my Open Beta and see if the servers are the same... I'll check for you.

New updates always goes to Beta First, last update for Stable/Released Version was to bring Stable/Released Version to the same build as Open Beta which was 2.5.2.xxxx. In other words last Sable Version was to introduce Persian Gulf map and Hornet. Once they are satisfied to latest patches and updates of the Open Beta, Released Version will benefits another update. You don't want new features going live on a Released Version without knowing how it can react as Alpha's, Beta's etc.. are there for that reason.

New updates always goes to Beta First, last update for Stable/Released Version was to bring Stable/Released Version to the same build as Open Beta. In other words last Sable Version was to introduce Persian Gulf map and Hornet. Once they are satisfied to latest patches and updates of the Open Beta, Released Version will benefits another update.

I personaly put them in Saved Game Folder using OVGME. Saved Game Folder is not affected by the updates, so basicly you could, i think always leave the liveries loaded, while in Game Folder, you should disable the mods before updating. And stuff in Saved Game folder usualy doesn't affect Integrity Check. Saved Game Folder allow you to put all liveries in the same folder under Liveries and Cockpit lieveries also goes in the same folder, while in Game Folder, you got some in Bazar, Some in Core Mods etc... Run a repair, in Game Folder you'l loose them if not using a GME like OVGME, put them in your Saved GAme, repair or updates DCS and they stay there. I do this quite easy, i have one Livery folder and OVGME points that folder to DCS Open Beta Saved Game and DCS Released Version Saved Game. EDIT: The only thing with droping them in your Saved Game Folder, if you work on liveries yourself and wanna see them in ModelViewer, you need to modify the top oh the ModelViewer'S autoexec.lua to point your livery textures. mount_vfs_liveries_path("C:/Users/.../Saved Games/DCS.openbeta/Liveries") LoadModel("CoreMods/aircraft/FA-18C/Shapes/fa-18c.edm") LoadLivery("FA-18C_hornet","Your_Livery_Name")

In today's post of patch note, i'Ve seen something, that i thought was something i was expecting, but seems to be diferent: https://forums.eagle.ru/showpost.php?p=3553296&postcount=16 Added abeam distance to course line. I thought this was the Cross Track Error Indicator/Perpendicular offset , but seems not and i got this update confused, if so it would had been on the HSI botom right handed corner (linked image, should apear below bearing on number 11), but nothing there so it's something different, anyone knows what it's actualy is and how to enable it in the HSI?