-
Posts
233 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by PitbullVicious
-
I've found that the CH Fighterstick is pretty much ideal for Gazelle, light and accurate. I fly with it without any curve adjustments.
-
Thanks!
-
How does the radar gimbal work during LTWS / TWS, when one sets their horizontal scan to narrow (let's say 80 degrees)? Is it still possible to crank up to 70 degrees, keeping the L&S target(s) still within the radar beam? I.e. will the radar gimbal so that it will be scanning 10 degrees right of the nose and up to 70 degrees left of the nose, when cranking right, or does the crank have to happen within 40 degrees of one's nose in order to keep the lock (i.e. radar center is always pointing directly from the nose, when in L&S lock and narrower scan)?
-
What does the EI stand for on the HUD time indicator?
PitbullVicious replied to imacken's topic in DCS: F/A-18C
I think it is feature of Finnish Hornets. "Ei" (pronounced "ey") in Finnish means "no" and we tend to be a bit negative as a nation, so it's always an "ei" time. -
Description: A friendly plane shows up as hostile after cold start on a multiplayer server. IFF is on, D/L is on, target is interrogated with sensor switch press. Trackfile: https://ufile.io/j1woz Date and situation: Blue Flag server, 2nd of March, about 1-2 p.m. GMT. Steps to reproduce: Unknown. Seems to be a random error. DCS version: 2.5.4.28090 System Specs: See signature Video of the bug (recorded from a track file): Description of the video: Start from Khasab, with 2 HARMs and two IR Mavericks, planning to attack Queshm. 0:03 Turning my IFF and Datalink on. 0:17 You can see the picture on my SA page, just before taxing. 0:30 After take off, I turn on my master arm, set my counter measure program, start the cool down with my mavs and set the radar. 1:10 You can see me interrogating one radar contact, that returns as friendly. 1:18 At Queshm, I suppress an SA 11 with HARM and close in for a kill with the Mavs. 1:30 A hostile contact pops up on my SA page. 1:54 Turn back towards Khasab. You can see a cold, hostile contact on my SA page. 2:38 The hostile contact jumps. I didn't notice this during the actual flight. 2:51 I notice that there is a hostile contact too close for comfort and turn towards it. 2:58 It turns into an ambiguous contact. 3:06 After I interrogate it, it again shows up as hostile. 3:21 Fox-2 3:45 Fox-2 again 4:30 Fox-3 which finally connects. 5:00 A friendly hornet then finishes the kill, which seems to indicate that I wasn't the only person who saw the contact as hostile.
-
I think now you need to lock with STT (later LTWS / TWS will also work). In addition to being within 20-25 miles with your target having a low aspect angle (hot towards you).
-
If it still works (haven't tested it for a while), I can't recommend the DCS Kneeboard Builder enough :) http://www.dcskneeboardbuilder.com/
-
GPS implementation and JDAM and JSOW
PitbullVicious replied to PitbullVicious's topic in DCS: F/A-18C
Thanks RShackleford for the explanation! -
GPS implementation and JDAM and JSOW
PitbullVicious replied to PitbullVicious's topic in DCS: F/A-18C
Oh, I meant if the drift in INS is implemented before GPS implementation. I think the updates have only talked about INS being worked on, not the GPS (although I'm not sure if it was only the INS alignment that was mentioned). Edit: Just verified, there was only talk about INS ground and CV alignment, nothing about drift (or GPS). -
I always thought that Hornet GPS would be required to be implemented before JDAMs and JSOWs, but now it looks like the ordinance will be implemented first (unless I've missed something). I think currently the INS is absolutely accurate and doesn't model drift yet, but according to another mini-update these are in the works. If these come out before GPS implementation, will we for the time have rather inaccurate smart-bombs? Or will they just assume GPS is running and accurate separately from navigation? I guess this is more me trying to understand the development process rather than saying "it can't be so" :)
-
Just a quick note (without commenting the Gazelle itself): The stream doesn't seem to be the most reliable thing to judge what is actually happening. I've noticed that due to latency DCS engine seems to sometimes "interpolate" movements somewhat suspiciously. For example in Helicopter Tournament 3 stream you can see me what looks like a loop in the stream, while no such thing happens if you look at the view from my client side. If you compare this: To this: The flying on the stream seems quite different, dare I say more "arcadish", than it looks from my perspective. P.s. The tournaments have been a blast! :)
-
Thanks again Alpenwolf and 104th! It was great fun, and the stream was really good (looking at it afterwards). Maverick got all hyped up, and for good reason :D It was like combination between Apocalypse Now and every Michael Bay movie ever. Red's rocket attack was just beautiful to watch. And extra special thanks to Commie for the GCI. It really made it a match (and sorry for jumping the gun in the beginning :) ). The only downside was quite a few technical problems from my own side. My joystick started to give spikes just before the tournament, so I had to use another one, which I haven't used to fly the Gazelle before, my Oculus kept losing its sensor and I had to switch to TrackIR in the middle and my DCS crashed twice... Despite all of the above, I had really good fun! Waiting for the next one.
-
PitbullVicious + Pantzman - SA 342L
-
I'm quite sure that it refers to the HOTAS button (switch?) on the throttle being usable to change the FOV of the Maverick missile (it wasn't functional in the last update), not that we get HARMs. That button has different functionality depending on which weapon / instrument is active. In case of HARM it changes / progresses the sequence (what ever that is, I'm not familiar how the HARM works), and with the Maverick (and possibly with ATFLIR, once we get that) it changes the FOV.
-
reported earlier [REPORTED]Master Arm On to Dispense Expendables?
PitbullVicious replied to Nealius's topic in Bugs and Problems
Have you turned on your ALE-47 from the EW page on your DDI (it's on standby by default)? -
Hah, would like to hear that :) Sent from my Moto Z2 Play using Tapatalk
-
Here's a video from Varis' and mine last flight, and the knife fight with 104th_Mustang, around 01:02:20 mark in the original Twitch stream, as promised:
-
Multicrew - Can't slew camera left and right
PitbullVicious replied to DrummerNL's topic in Bugs and Problems
Me and mate tried themulti-crew (open beta version) on the Persian Gulf Blue Flag server on Saturday and were surprised to find the Vivianne slaving and lasing working on the M-model. Wonder if something was fixed by ED in one of the recent patches... or if the stars were just aligned right. We did have problems with the Nadir system in multi-crew, though (it didn't seem to finish the alignment properly). -
Thanks a lot! Me and my co-pilot had great fun :) Ate a couple of Vikhrs and got into a good knife fight with one Ka-50 with my last life, and got my first kill (just to be killed by another Vikhr soon after). Video coming up later! Hope we'll have GCI also on the blue next time.
-
Regarding of the above, I'll add him here for now (hope this isn't too late): PitbullVicious + Pantzman - Gazelle L (Note that PitbullVicious has already been registered individually, I'd like to add Pantzman as my co-pilot)
-
My friend might want to join the ride (so to speak) as a Gazelle co-pilot with me, but I'm not quite sure from the mission description if this counts as extra player towards the 20 limit or not. Could someone elaborate?
-
PitbullVicious - Gazelle
-
Alerax's LSO AI Script
PitbullVicious replied to Alerax's topic in Utility/Program Mods for DCS World
I've been looking for a long time for that next best thing since sliced bread, and today I think I finally found it. Excellent work! -
I'm not sure if this is what you've tried out already and is limited, but using RCTL+RSHIFT+NumPad / and RCTL+RSHIFT+NumPad * (IIRC) should move your head position back and forward, without needing to lean anywhere. You should also be able to save the head position with another key combination (RCTRL+RAlt+Enter??) for future use.