All Activity

Could that mini stick be used for the mouse control in the cockpit? Seems like that might be awkward or a conflict. Can’t figure a use for a second analog stick. Good that it can be reassigned then.

With the Quest Pro; Comfort is awful unless you get a third party strap, I get a headache after a while. With the pancake lenses you get edge to edge clarity on the QP, as opposed to a sweet spot on the PSVR2 with its older Frenel lenses which makes things less clear outside that spot. The LED panels on the QP while lower resolution are sharper for things like text due to its subpixel arrangement (full RGB stripe) as opposed to the OLED panels on the PSVR2 which uses a pentile arrangement where some pixels share subpixels. On the other hand the PSVR2 has much better contrast, particularly notable on night missions where you either have grey black skies (with local dimming off) or lots of halos (with local dimming on) while on the PSVR2 it’s a true black and just looks spectacular. Other things like looking into the sun or bright clouds are much better on the PSVR2 when they get washed out on the QP. The other big difference is the PSVR2 is providing native display port output while the QP is sending a compressed data stream. Firstly there is an overhead to that compression (even though most graphics cards handle it very well) and there is decompression required on the headset side which eats battery life. The second is that no matter what people say I do notice compression artefacts, particularly on things like the sky. Another factor I noticed is that the stereoscopic vision is better in the PSVR2. It reminds me of when I first put a Rift S on and was blown away by that feeling of being in the cockpit. The Quest Pro feels a lot more like you’re watching the game on a screen to me. Ironically both are helped a lot with a third party strap, the quest pro can be made more comfortable (albeit still not brilliant), and the sweet spot issue on the PSVR2 is helped a lot by having a third party strap so you can get it stable on the sweet spot. I use the Globular Cluster kit on both headsets. The way I would summarise it is that if my absolute 100% priority was having the cockpit as sharp as possible I would go QP over PSVR2. On the other hand if the environments and immersion are the most important thing (which to me is kind of the whole point of VR) the PSVR2 is by far the better of the two now that the performance can be so good. Do a nighttime cat shot in the PSVR2 and you will understand.

Currently, f4 is unplayable buggy/immature/lack of information/etc. For various reasons,

Bye Phant

It's worth doing this with all of the small analogues (flaps lever, slider, mini sticks, etc). One you've got it setup it's easy to assign either way depending on the game/module.

This is very sad! I still hope to see a new 3D model for the Kiowa, as well as textures. I also hope to see the flight model fixed. The Kiowa isn't that agile, much less able to hover with 100% fuel and 4 Hellfires equipped. It's very agile, and I've seen pilots commenting that it can't do this in real life due to its weak engine. The comments were made on Polychop's own Discord. I'm still hoping to see these fixes in Kiowa!

Thank you for the continued research. Hoping ED listens to feedback and includes some critical Soviet infrastructure.

Hi, For any of those with experience - what graphic settings could I run a Crystal Light at with a i9-14900KF, 32.0 GB, RTX 4080 Super I currently run a 4k monitor with pretty high settings, and I'm not sure what I could expect from that headset - how much detail do I lose to gain 3D & which is worse for immersion... If I knew what I'd have to run it at I could see what that looks like in 2D (pop up etc.)

A Cessna might be fun for learning fundamental proficiency in flight procedures like ILS /Instrument flight etc. but not sure where the Combat part of DCS comes in.

Спасибо за информацию. Не когда не интересовался историей игроделов. Разве что немного про ОМа и Петровича. Да и то в связи с тормозами выхода "Битвы за Британию" у первого и "телепортом" Петровича из ЕД в проект РОФ. Остальное мне всегда было по барабану.

Ah... same issue here. Thanks for the FYI gents

Have you tried the OV-10 Bronco mod? It's fantastic.

That is caused by DLAA, and DLSS only makes it worse. You can "fix" it by using other anti aliasing method, like TAA or MSAA.

Anyone else's fuel probes not showing up in game? Have on the M.E. but never in game...

I see that,firstly, I had NPI 2.4.0.08 which didnt have exactly the same editable lines.In NVidia App,I changed the settings for DLSS overide to"Use the 3D application setting". After a lot of back and forth I now have DLSS 310.4.0 with preset K. So far I dont see a difference in graphic quality,although maybe(wishful)a bit less shimmering. Thanks for all the helpful replies.

Sweet. Does this work in MP?

Так то да. Даже сам подраздел BAM в мануале находится в разделе даталинка. Просто в рамках взаимодействия с ИИ CPG в игре это становится ещё и инструментом ограничения зоны поиска целей, которым игрок пилот кочет объяснить Джорджу в какой зоне искать цели. Тут замечаю три вещи: - он и правда довольно точно при сканировании TADS остается внутри зоны. Не знаю, насколько точно он игнорирует попавшие в FOV объекты за пределами зоны, но с этим пока не видел отклонений. - почему в интерфейсе ИИ CPG из списка Area Searches, относящихся к фиче Battle Area Management, доступно только OWN PFZ, а ACTV PFZ не получается подсветить и пользоваться, не взирая на активацию PF в BAM TSD? Это известная проблема или я не туда понатыкал? - бывает весьма не просто сопоставить район обнаруженной цели с тем, что мы видим на растровой карте на TSD, чтобы потом взять и точно обрисовать PFZ/NFZ. Особенно, если рядом нет населенных пунктов, зато френдли и противники близко друг к другу. Понятно, что в жизни это не сильно нужно может быть. Да и пилот имеет возможность рисовать зоны точно, попросив CPG посмотреть на углы зоны с лазерной дальностью и наблюдая отметку TADS на TSD (особенно ловкий CPG может этот финт самостоятельно исполнить). Пока писал, нарисовалась идея: Просим Джорджа смотреть в предполагаемый угол зоны (прямой PHS Search) и получить лазерную дальность (Lasing), а сами ловко тыкаем углы зоны ровно в крестик TADS на TSD! Черт, это страшный вертолёт Шорт лист обнаруженных целей может содержать их аж 16 штук. Если его утвердить Джорджу и разрешить самостоятельное ведение огня из пушки, то этот горячий парень так и сделает - загрызет их всех последовательно, всех, которых не потеряет из виду при маневрировании. Мешают тут только две замеченные вещи: - порой он слишком рано переключается на следующую цель. Очередь еще не покинула ствол, а пушка, следуя TADS, уже перенацеливается на следующую из шорт листа. Это чаще приводит к еще более быстрому поражению целей, но иногда и к «подранкам». Торопится, короче. - достаточно часто он принимает команду на стрельбу, но не стреляет, долго не стреляет. Тут помогает длинное прожатие кнопки согласия на огонь, которая теперь стала контекстной и на этапе Target Tracking & Engagement подправляет наведение TADS (функция ADJ+). Должно ли быть так?

Or save the Group as a Group Template, so you can use it on other missions as well.

I've finally had time to actually try your repo and just wanted to say THANK YOU for getting this working. I talked to Brian a couple of days ago and he was going to turn on the UHF frequencies soon (within the next week was what he had hinted at). I may have to shoot him a reminder but it was on his list to get done. Any chance at getting the AH-64 and CH-47 working with this in the near future?

As some may know I service SoHo and smaller companies like up to ~25 people, nothing too big, so it's relative comparable to what can happen to you, me, everybody. Today was such a day, nothing really special, replace old HW with Win10 with 6 new Win11 Pro clients which put together, GB-B850-9600x-1TB 990Pro-Seasonic Platinum 500w fanless-32GB_6000 and a DarkRock-5 in a nice and quiet bequet tower. The building was fun despite 1 MB was DOA, but they just flew. Did that 2 weeks ago and today I planned to roll them out. Save Data and Mail from old PC to server Setup local LAN static IP and DNS rename PC join AD setup accounts install all LAN printers restore Data and Mail rinse & repeat...1..2..3..4..5..BANG !!!!! I accidently ended up on the wrong desktop, i was in RDP on Server instead of on the local Desktop, both had 2 File Explorers open, Task manager, windows over windows, I opened the the RENAME THIS PC on the wrong Desktop !! ME IDIOT !!!! I RENAMED THE Active Directory Controller, AD-DC, to PC-3 !!!!!!!!!!!!!!!!!!!!!!!! hit OK and then found out FUUUUUuuuuuuu§& WRONG RDP --> WRONG FILE EXPLORER --> WRONG CONTROL PANEL -----> GOD DAMN WRONG MACHINE to rename and I picked the worst machine you can possibly rename while in production and running THE DOMAIN CONTROLLER My blood froze, my pulse went to 180 from chilling low 60s, my promise to be home at 19:30h THE LATEST suddenly became a lie and my biggest fear was: "You're gonna either have some damn luck, PRETTY SOON, or you end up with Acronis, putting the Backup from last night on" Ya, after you made the bootstick, 20min, went upstairs to the server. a real ClusterFu%§ visualising what was ahead of me if I didnt come up with something quick, quickly . So, I know how to rename a DC, you DON'T do it like you do with any other Windows machine, it's a Powershell command, 3 of them iirc, with reboots and DNS entries. Not complicated, but must be obeyed or you screw up the directory, or your access to it...f you only run 1 DC, that must be said to be fair. OK..Google... it says...you did the WRONG thing, there is NO easy way out, you either use a Backup or REINSTITUTE the Domain, which basically means you might as well reinstall the whole damn thing, that's 1 day alone if ALL goes right. I did that server and it is not difficult, just a lot of stuff and it takes time and care. So...I had no choice.. I had to reboot it while I was there, no way out, you dont want to expore the outcome of that 40km away and only VPN,Teamviewer/RDP/VNC at hand. OK, the server has an Enterprise Dell iDrac that I can access from here, that would have worked even from remote...but here it goes. So I rebooted, there was no "rename again" back to SRV possible, it needed the reboot to commit. So I did. It booted to login screen, so far so good. At least no AD DB error while booting, that is a total mess then. OK, OK...so far great...try to login.. Login as admin and pwd --> Red Pop-Up --> No security entry in AD Database for this workstation. Login denied! OHH SH!T You cannot log into the local domain aka PC/Server on a DC, it is ALWAYS a log in into AD-admin. So I could not do SRV\administrator to log into the Server locally w/o Domain. I tried despite I knew it wouldn't work and it didn't, waah ! You're finally screwed !!!! You have a booting 2022 AD-Controller with a wrong name that doesnt connect to the network, doesnt show shares you could connect to and SOMEHOW work, heck, if the SQL's would run, I'd have more time to sort out things...but this beast doesnt do ANYTHING but boot to Welcome screen and sit there forever. mI also couldn't even finish the 6th PC and drive home, I was about to join AD when that happened There is no guide on Google or in AI that tells you how to redo that mishap. It's a nail in the server's coffin that you usually don't get out again. That is what gave me headaches, the not having options to fix it, just FIX IT, god damn, it's only a few lines of code...ok maybe a few more it's AD and thus deeply DNS integrated...WTF, how could you fall into exactly this pit, this No-Way-Out pit, with a big "How to Sink a DC" sign above it in Neon. Aaarghhh, a big client..and you screwed up his DC, it better runs Monday morning 7am, no matter what, no matter. So...I have it all on Acronis on a Linux Server as well as in Acronis Cloud, that would be the ultimate thing to fix it if I didnt come up with a solution, something dead simple, stupid simple, as quick&dirty as the renaming was. But what. OK,...lets try F8 and Safe Mode, maybe there is something that can be done.....but wait....I cannot reboot or shut it down. The DC-Server Welcome Screen in contrast to Client Windows OS has no Button to restart or shutdown, it's a safe guard. Well, lets see Dell's iDrac....but there have never been drivers installed in the OS for any iDrac, so I did not expect see a graceful OS shutdown/reboot option, just the normal AC operations which I knew. I was right, no graceful options, warmstart or cold restart or OFF. Yeah, what a freaking nightmare, I have to reset the server now as well, a Russian Roulette with AD Database and RAID's, you never reset server unless you really really really have to. I had to ! Show balls !! Grab it btP ! I hit warm restart and was then greatet with a UEFI Secure Boot error, luckily I could just say "screw you, I already have enough trouble!" and clicked it away and it kept booting through the many Dell UEFI and FW screens, I kept hitting F8 over and over agin. Made it, Boot options came up 1 to 9..or 0 god knows. 4 is Safe Mode.... but wait....boot to LAST KNOWN WORKING CONFIGURATION ! ???? OK, that is not ment to fix any AD structural damage if there is any but it should rewind the actual PC-settings I changed a reboot ago !? Let's try, there is really nothing to loose but the 5min it takes to boot. If it screws up and crashes I go the Acronis route, chill and wait until restored, if Acronis lets me down I am screwed, then I am gonna spend Sunday here, for free, fixing my sh!T. Monday 7am is deadline. The server booted, as before, login available, no errors so far....now try the usual DOMAIN\administrator PWD and see if it locks up. TATTAA....It fixed it, dead simple decade old rescue option fixed the misconfig, in a very lucky way I admit. The narrow path with too much domain on one side and too severly misconfigured HW on the other side, this option was golden, it saved a lot of work, money and effort. And I, I will, after 30 years, watch even closer now..on which RDP or Desktop I am before I rename a machine in a Directory ! I really felt baaaad the first 5 minutes after it happened, the"You screwed it Up!" hit hard. Anyway, that server booted as nothing ever had happened, DNS was correct, DHCP changes I made were also still present, all good. Fixed that last PC, printers, users, Mail, done. When I got home, 2h late, my step daughter looked at me, said "You know how late you are!!?" went out and took off...LoL I still felt great, still do, having a beer and typing this.... better than installing a 2022 SRV with AD, Rolls, Software, Users and what not else till 2am and all Sunday too. Done that, thank you, my beer tastes a lot better than that ! God save the command "Revert to last known working configuration" Prost

That did it, Thank you!

Thank you so much for sharing... NOT!!!

Thanks for the update. I should have posted a correction a long time ago. I currently running 576.52 and the problem came back so I'll have to troubleshoot further to see hat the problem is. If you don't mind, could you try it again? I'm just wondering if I was able to get into safe mode because the reversion wasn't followed by a restart prior to trying to get into safe mode.

Cheers for the chuckle