Elliot
-
Posts
53 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Elliot
-
didn't the f14a have a total thrust of aprox 34,000lbs? those figures look to be more for the B
-
can confirm lmao
-
should i delete this thread considering there's two other ones on the exact same thing?
-
that makes sense, i wondered why there was no change. so i'm assuming the 'test' is more of an aesthetic feature rather than a functional one anyhow thanks creason, you helped alot
-
i tried pulling it a while back but the MCB test switch always showed the circuit as working, and plus, there was no difference in terms of compressor stalls i'll test it again though
-
oh, so it's been fixed? many thanks, i was unaware until now
-
does that include not fixing the breaker? or will it be the last time you ever touch it after fixing it
-
speaking of that, is there any news on when that is coming out?
-
that's the thing though, i kinda prefer the A because of how much she makes you work for your kill, whereas the B is just boom and zoom not to mention the A begins to go zoom at high speeds, inlet ramps go brr
-
that is true, however, the only time i ever seem to get a compressor stall in the A is when i yank back on the stick at idle and really slow, or duing rapid AOA transitions, but if it's a constant AOA, nothing usually happens. if you ask me, i'd happily exchange some of that engine stability for my thrust back. and at the end of the day, if the breaker stays modelled, we could always turn it back on to prevent such issues from happening
-
I'll take my second question as a no then, but what about the test switch? will it remain functional or will it become unclickable as it won't have a use
-
if so, will the test switch remain functional or will you make it unclickable (as it will no longer have a use) also, instead of plain out removing it, could we have a vote on removing it? it kinda feels unfair just to break the news right as i wanted it fixed
-
Bug: Hello. I would just like to submit a report that the Mid Compression Bypass breaker pull keybind in the F14A Tomcat is not functional. Can I reproduce it 100%: Yes How to reproduce: Step 1: Open the fuel probe Step 2: Pull the breaker Step 3: Throttle up to mil power Step 4 : Switch to the RIO seat and do the MCB circuit tests, + check power output Result: Both of the lights will stay lit, indicating the circuit is still functioning. In addition, no thrust is returned. DCS Version: OpenBeta 2.8.6.41363 System Specs: CPU: Ryzen 9 5900X GPU: NVIDIA Geforce RTX 4080 RAM: 64GB 3600MHZ DDR4 (quad 16gb sticks) SSD: Samsung 980 Pro (iirc) OS: Windows 11 Pro Peripherals: Joystick: Thrustmaster TM16000M Throttle: Thrustmaster TM16000M Pedals: None (slider used on throttle) Others: None Headtracker: VR (rare occasions) Mission File: Instant action freeflight (also doesnt work anywhere else, including multiplayer) Log: see attached Track: see attached Video/ Screenshots: see link https://streamable.com/vb86yv Mods: Core sounds mod (Echo19) **I tested it both on ST and MT, no luck for either of them also sorry for the blinking in the video, it's likely just a thing for me (it doesnt happen ingame, only out of tab and during videos) dcs.log bug.trk
-
k
-
Mid Compressor Bypass Breaker - Where is it?
Elliot replied to Southernbear's topic in DCS: F-14A & B
yeah, i think the keybind is open, even with the probe open and the speed maxed out i cant see any change when i try to pull the breaker it's a shame, i want my compressor stall heaven + thrust back not to mention, a jester voiceline saying its pulled would be nice; either that or something in jester's 'within visual range' menu -
Mid Compressor Bypass Breaker - Where is it?
Elliot replied to Southernbear's topic in DCS: F-14A & B
i'm aware of this, but the MCB test lights show that both engines have power to the circuit - isn't that implying the breaker hasn't been pulled? -
Mid Compressor Bypass Breaker - Where is it?
Elliot replied to Southernbear's topic in DCS: F-14A & B
is it broken with the recent dcs updates? the aircraft doesn't feel any different and the test switch shows it as working even after it's been pressed -
does it turn back on if you switch to the rio pit? i can't seem to get it to work as the MCB test switch lights always stay lit
-
i'm aware you don't gain thrust, but you get what was lost back the keybind just seems to be broken atm, i can't see any change
-
i did try, but it didnt seem to do anything, very unfortunate, i like my underpowered turkey
-
thanks for the info, and i also did try the power tests but both lights stayed lit no matter what, i'm thinking the keybind is just broken
-
considering this topic is dead, could we atleast get a jester voiceline telling us the breaker is pulled so we know when we're getting our thrust? thanks
- 9 replies
-
- 1
-
-
- mid compression bypass
- f14a
- (and 2 more)
-
There's a bit of a lack of info on this in the F14A, so I just want to ask a few things: How do we know when it's on or off? Does the pilot keybind transfer over to the RIO seat (like the countermeasure dispenser?) Is the button a toggle or a push button you have to hold? Is the breaker itself in the RIO pit animated? Is it still working in this version of DCS? I've tried to pull it in both the RIO and Pilot seat, but the MCB test switch still shows it as working. Any help would be appreciated, thanks!
- 9 replies
-
- 3
-
-
- mid compression bypass
- f14a
- (and 2 more)
-
The problem with ASW though is that it looks garbage, you get a ton of artifacts for barely any extra performance. A good example is when you look at a sidewinder on the wing of the F-18 and begin rolling; it appears like the sidewinder has some weird motion blur. DLSS 3 would be better, it has dedicated hardware instead of software-only frame generation.
-
Not that I know of, I double checked my controls and it has no conflicts, and the issue only happens in the F-14, not in the F-18 or SU-33 for me. Edit: I've noticed it seems to happen when I use the L2 (10) button on my HOTAS, I'll see if there's a conflict with that button. Edit 2: It seems to have fixed; I had another modifier for the same button (off). Seems to be that was causing the issue. Moral of the story: avoid having 'off' variants of the same button, the only time you use it is with a switch.