All Activity
- Past hour
-
Shack started following Instrument panel for Winwing MIP instruments on my DOF reality P6
-
90-s
-
So, ditched the pilot mdl. and went with what looked right and worked the best, as far as distance, windscreen view, and gunsight utility. Currently, that's: SnapViews["F4U-1D"] = { [1] = {-- player slot 1 [1] = {--LWin + Num0 : Snap View 0 viewAngle = 54.750000,--FOV --FOV Cockpit Zoom 54.750000, 55.000000, 54.000000, OEM 85.000000 "F4U-1D" viewAngleVertical= 0.000000,--VFOV OEM 0.000000 hAngle = 0.000000,-- (Snap View)/(Cockpit panel view in)(-30°) vAngle = -30.000000,-- Cockpit View 0.000000, OEM 70.000000 x_trans = 0.046000,-- Cockpit View In_Trans 0.046000, OEM 0.150000 y_trans = 0.040000,-- Cockpit View Up_Trans 0.040000, OEM 0.030000 z_trans = 0.000000,-- Cockpit View Rt_Trans 0.000000, OEM 0.000000 rollAngle = 0.000000, cockpit_version = 0, }, [13] = {--default view viewAngle = 40.000000,--FOV Cockpit Zoom 40.000000, 40.200000, 39.420000, 37.500000, OEM 85.000000 "F4U-1D" viewAngleVertical= 0.000000,--VFOV OEM 0.000000 hAngle = 0.000000,-- (View Center)/(Camera Snap View Down)(-30°) vAngle = 0.000000,-- Cockpit View Angle 0.000000, OEM -11.500000 x_trans = 0.046000,-- Cockpit View In_Trans 0.046000, OEM 0.150000 y_trans = 0.040000,-- Cockpit View Up_Trans 0.040000, OEM 0.030000 z_trans = 0.000000,-- Cockpit View Rt_Trans 0.000000, OEM 0.000000 rollAngle = 0.000000, cockpit_version = 0, }, Bowie
-
-
Noble's Helmet Camera
Tactical_Joker replied to Tactical_Joker's topic in Task Force Trident's Squadron Media
-
Scotch75 started following F4U DevGru - Check This Decimal Point
-
MAXsenna started following Can I just say... and Access to the manual before release?
-
Time flies in the sim world...
-
Saved Games ist ein Systemvariable, die standardmässig auf c:\benutzer\<benutzername>\saved games zeigt. Es reicht daher nicht aus nur das Verzeichnis physikalisch zu kopieren. Auch die Systemvariable muss in Windows entsprechend geändert werden.
-
They probably will when modules get updates/re-releases. For the time being, have you had a look at Quaggles Input Injector and Munkwolf's keybind repository? It was ET.
-
Found that 'kjz = 1.25,' was dragging the nose around a bit in yaw, so went back to the initial gambit of '+1', in this case a 25% reduction from that previous setting. Moved the decimal point back on kjz, and then added "1": 894 kjx = 2.25, 895 kjz = 1.00125, Much nicer in yaw, and just a bit more sensitive in pitch, but the Inertia is still there. Set the 'X' and 'Y' joystick curves from 19 to '21' both. Really flies nice, and a good gun platform at boot. Bowie
-
can not reproduce VR: HMD / HIADSS Symbology too high
bak3dp0t4to replied to Bracketman's topic in Virtual Reality
@Phantom711 If it made a difference I'd extend you the same offer I extended BigNewy; If it would prove to you that I and the dozens of other people in this thread are not full of dung, you can literally come to my house, put my headset on, and see it for yourself. Putting on a physical Quest 3 headset is the only way you are going to see this issue. 20 minutes of flying around in the Apache with your torque gauge at the very top edge of the headset screen and flying around everywhere staring through the slip indicator instead of the flight path vector and you'll be ready to pull your hair out. I'm literally getting neck pain after a 2 hour session from having to keep my chin buried in my chest and looking out the top of my eyes the whole time. In case you skipped over what @actually_fred wrote: "Yeah, this sounds like DCS is incorrectly assuming a vertically symmetrical FOV and incorrectly drawing in the center of the image it submits to the headset, when it should be putting it in the center of the field of view. It should be expected that this issue can not be reproduced with a Pimax Crystal, because Pimax Play reports vertically symmetrical FOV. DCS is provided with the information it needs to do this correctly when it calls `XrLocateViews()` -the `XrView` array members have a `fov` member, which in turn has separate `angleUp` and `angleDown` members.These are not required to be identical, but for a Pimax Crystal, they are, so you can't reproduce the bug on a Crystal. Pimax Crystal: angleUp is 0.90541315 (radians), angleDown is -0.90541315 - ~ 52 degrees both directions Quest Pro: 42 degrees angleUp, -53 degrees angleDown, so a crosshair that is put in the center of the render target without paying attention to the FOV angleUp/angleDown will be quite substantially off. These are the values that the runtime reports to DCS and that DCS should be using, not a personal subjective measurement. You must use a real Quest headset to test this issue; the Meta XR Simulator always reports symmetrical FOV. It is also likely that this ties into the reports about 'mirror window too high' - though that isn't a bug if it's accurately showing what's sent to the panel." As I explained to BN in a previous post, for it to line up properly I have to pull my headset so far down on my face that the forehead pad is literally sitting on my eyelids. The picture is completely blurry and I'm basically looking through the top 1/4 of the lens to see straight ahead. The alternative is to try to angle it downward/forward, but a: the headset doesn't angle that far, and b: if you slide the strap up high enough it's no longer contacting the back of your head and theres about a 1-inch gap between the top pad and your forehead. Would either one of you care to explain to me how that is a proper fitment? Also, surprise surprise, this is an issue with other games when played on the quest 3. Check it out: https://www.reddit.com/r/oculus/comments/187e2uj/huds_too_high_on_quest_3/ https://www.reddit.com/r/OculusQuest/comments/177bac3/huds_appear_off_center_too_high_on_quest_3/ And just like with bignewy's pimax crystal, your quest pro is not a quest 3, which I can't believe I actually have to explain to the both of you is a different piece of equipment that works differently than your quest pro or his pimax crystal. I didn't have this problem on my CV1 either. But I DO have it on my Quest 3. What you two are basically saying is if you said your chevy has an engine knock I'd tell you you were wrong because my ford doesnt do that. Do you see how... (I cant really think of a nice way to say it)... that sounds now? -
Yurgon started following AMD oder Intel für DCS?
-
Das einzige was du dafür brauchst ist eine Verknüpfung auf bin\DCS_Updater.exe. Sowas kannst du dir auf den Desktop legen oder an "Start" oder in der Taskleiste anheften. Registry-Einträge sind nicht mehr erforderlich. Wenn ich Medic richtig verstehe, will er Windows neu installieren. Warum sollte man da mit irgendwelchen Links rumfummeln? Ich würde einfach vom alten PC Gespeicherte Spiele\DCS vollständig auf dem neuen PC nach Gespeicherte Spiele kopieren, und das wars. Wenn man das vor dem ersten Start von DCS macht, sollte es sofort und ohne Murren starten. Hat jedenfalls bei meinem letzten Umzug auf ein neues Windows anstandslos funktioniert. Ich musste nur die Einstellungen alle etwas hochschrauben, weil auch bei mir ein 7800X3D werkelt und ich damit sehr zufrieden bin, was der so wegwuppt.
- Today
-
Just to clarify, if you're talking the ability to hand off targets via FCR to flight members for Situational Awareness or targeting, that is implemented as the RFHO, and can be sent to Primary Datalink members. The FCR targets can be sent for only SA purposes via the TSD->RPT->TGT->All (if I remember the procedure correctly) to Primary Datalink members. Issue with BAM is that panning the TSD causes desync, so when you draw the zone and it activates, it doesn't go where it ought. Same thing with the CAQ point.
-
Please, the flight model and the desynch of the TADS on multicrew is tiring. Correct me if I'm wrong but the FCR H-O was never implemented? BAM were never useful on multicrew because it never worked and radio presets also have label desynch. Also on multicrew the AGM-114L never hits using laser designation but using FCR its almost a 100% hit. I guess this is because of the TADS desynch. The Route Tool it's also not synched. When the CPG enters the aircraft it doesn't have any waypoints. What about the RFI and ECM? DTC? Also the 1 unit on airbase not letting for another crew member is also silly, but this is for any aircraft not only the AH-64D. It makes runnig dynamic campaigns a bit hard. Oh, and I forgot about the day 1 crash bug, if you enter as a CPG on cold start AFTER the aircraft was started it crashes the game for the CPG.
-
Ja, mit Zusatz-Tools (ShutUp10++) und über Umwegen (Registry) "noch" zu bändigen, aber wie lange noch, und mit welchem Aufwand? Der Rest ist Geschmackssache oder auch Leidensfähigkeit? Wir gewöhnen uns leider an jeden sch... siehe youtube, Prime, Netflix, Spotify, smart TV... das ging richtig schnell die letzten Jahre. Mittlerweile ist doch das halbe, von "uns" genutzte Internet ne immer größer werdende Werbeschlampe. Ein schönes Forum wie dieses hier ist noch die ursprüngliche Form des Netzes. Das erklärt auch warum ich hier gerne bin und mich wohl fühle, wärend ich mich wo anders nur befridige oder konsumiere. Und das geht erstmal so weiter bis... wir die Schnautze voll haben und ausweichen auf selbst geschaffene alternativen. Ich hoffe dass dies dann überhaupt noch möglich ist, denn die Rechnung muss in Zukunft wohl mit KI gemacht werden, und die gehört...
-
Special_Peanut joined the community
- Yesterday
-
DCS World 2025 Screenshots and Video Thread
JayGee replied to ST0RM's topic in Screenshots and Videos
-
Also refueling in auto, normal stick with springs. It's less of a fuss, one checklist item less, and the tankers tend to fly rather slow in any case, so the wings will be fully forward more often than not. The Tomcat is fairly docile during AAR, not difficult to refuel at all, though if you're low on gas, you'll have to hang in there a while.
-
Middle monitor showing left monitor when DCS focused
MAXsenna replied to Veen's topic in General Bugs
That's a bummer. I was planning on going triple screens eventually. Just a thought. There are so settings to set the bezel size, but I haven't tried that and don't know how it works. Do you think that would actually help? Cheers! -
two months......
-
And like @Raven (Elysian Angel) says. FFB makes it easier. It just does. One of the reasons are that the stick/"neutral" point moves when you trim. You always know when you are untrimmed physically in your hand, so to speak. Same for helicopters. It makes it even easier to understand what's happening. It will even teach you to not have a n00b death grip on the stick, because it's just more natural. For helicopters you don't even need FFB, just a stick without springs actually. I actually think this would work much better for any module when learning AAR. We need a clip!
-
It's entirely possible to beat the Mig 29 in the merge. As you merge keep on flying. The Mig 29 will run out of fuel catching you up. Manoeuver kill.
-
Out of curiosity, what type of DCS installations are you all using this software with? Is it DCS Steam Edition or the standalone version?
-
Danke euch und vorallem @Vpr81 der sich via p.m. gemeldet hat. Ich hab mich mit ChatGPT darüber ausgetauscht und es hat das ganz gut zusammengefasst: „Ich möchte kein System, das mich bevormundet oder mich für ein Produkt hält. Ich will volle Kontrolle, lokale Verwaltung und ein stabiles, berechenbares Setup, das meine Hardware optimal nutzt und mich in Ruhe lässt. Ich möchte meinen PC so nutzen, wie ich es will – stabil, performant, offline-fähig und sauber administrierbar." Und dass mir Home zu unsicher für die Zukunft ist hat es auch bestätigt: "Microsoft testet seine neuen „Consumer-Experimente“ (KI-Assistenten, Cloud-Sync, Werbeeinblendungen, etc.) immer zuerst in Home. In Pro musst du diese Features aktiv einschalten, sie kommen also nicht still & heimlich rein. Microsoft wird Home immer stärker verknüpfen, weil das deren Geschäftsmodell ist. In Pro können sie das aus rechtlichen Gründen (B2B-Nutzer) nicht so aggressiv durchziehen." Hab mich also für PRO retail entschieden. Werde da wohl in den sauren Apfel beissen und es für 170€ bei Proshop kaufen (absolut günstigstes) aber hilft ja nix. Linux geht leider noch nicht für DCS in VR. Und nein, ich kauf keinen Ramsch Key oder OEM für 15, 30 oder 50€, auch wenn das rechtlich "legal" und für ne gewisse Zeit funktioniern kann. Ich mach beim Rechner ungern halben Sachen und hab beim nächsten MB wechsel (vermutlich Lebenslang) keinen Stress mehr.