JumpinK

I'm just making my own fun out of this thread... ...personally for me it doesn't matter if the F-15E will come with removable CFTs or not. I'm eagerly waiting for my most favourite bird anyway! I don't wanna offend anyone here, but why not think "bigger"?! Meaning, it would be an awesome extra-realistic feature if the CFTs were removable but it is absolutely not necessary in DCS. I'm curious now whether RAZBAM will implement this feature of the Strike Eagle or not.

Ok. I'm out. Just one more: F-15E without removable CFT shouldn't be called full fidelity then. because IRL regardless of usage they can be removed! Sorry, i had to.

well... ...to me it seems that this video is the best argument for removable CFTs in DCS. :D

I don't get it, sorry. Because why would they ever build an aircraft with removable CFT's and then not ever remove them? I assume, they wouldn't be called CFTs if they had been modeled together with the rest of the airframe and if so they would not be removable then. No offence. Of course i could be very very wrong with my opinion, because I'm not an expert, just a hobby-aviator and a DCS-enthusiast.:smilewink:

What if the RAZBAM-guys do their developing-thing just as the MD-guys did their job on the real F-15 some decades ago?! I mean... First there was the F-15. Without CFTs of course. And it had it's own real flight model for sure. Some time later in development, when the F-15E had been launched, it was still an F-15 but with a 2-seater cockpit (like B/D model) + conformal fuel tanks. To make my point: It would be more realistic from the developers side to add those CFT's to the flight-model as it was done IRL. Like F-15 + CFTs = F-15E. Of course then it would be possible to remove them in DCS, because it would be already properly implemented. Just my weird opinion.

Hovering the harrier in 2D/TrackIR can be very difficult, because you just can't "feel" the movement and therefore being a little late on the controls can happen very easily which then often leads into PIO.:joystick: Hovering in VR (OculusRift in my case) is MUCH EASIER because you really can feel where your harrier wants to go and you are able to counter any unwanted movements much earlier than in 2D. (Just my opinion. And i also recommend VR to anyone who can afford it somehow, because it's awesome!:D)

As always, nice work. Thanks, Jabbers!

HEAT L, HEAT R is written in a tiny font on the display hence indicating an advisory message. It just tells ya, that your de-icing is on.

you just have to assign it once. AP-disengage/NWS-off/G-limiter-override is the very same paddle switch in the real jet and it's also just one button to assign in the options-menu.

Wags, could you guys please correct the modex-numbers on the aircraft?! It's dampening imagination a lot when my hornet has a 3-digit modex far from reality. As far as I know modex-numbers go from let's say (example) 400-414 (depending on how many aircraft on the squadron). I also found out that numbers x08 + x09 are unused (left out) in many squadrons but i could not find out why. Does anyone know more about that?! Edit: I'm referring to this link (might be a little outdated): http://www.topedge.com/alley/text/cvws/airwings.htm

I'm also wondering if it would be possible to implement increased repair-time caused by overstressing the airframe due to use of the paddle switch.

Depends on personal preferences, i think. I have the 10cm extension with the standard spring and it feels very good. Edit: No extension: green spring. <15cm: standard spring. 15-20cm: red spring. >20cm: blue spring. (That's what sahaj recommends on his site.)

2 options. option 1: make a spring yourself. option 2: buy a spring from sahaj. i would suggest option 2 since option 1 would mean a lot of experimenting until you finally get your spring right.

https://warthog-extensions-by-sahaj.com/ here ya go!

OpenBeta only! I'm kinda growin' with the sim... :D

Problem fixed! Thanks!

["fullScreen"] = true, Yes, I'm using windows scaling (@300%).

thanks for the response, guys.:thumbup:

yes, thanks. i have tacview installed and do use it. but as you mentioned, it's because of the beauty of DCS-replays at 4K!:smilewink:

Sure I do sometimes fly off the boat! But very rarely. Most of the time it's more important for me to be able to analyze my carrier-traps in replay therefore i have to set priorities!;)

This brought me to never starting my missions from a carrier deck again... ...missing the cat-shot-VR-experience a lot since then... ...unfortunately. :cry:

Maybe the VR/4K-fix has broken something in 2D monitor-mode now, if resolution is set above 1080p?! I have no issues running DCS on 1920x1080. Can you confirm functionality under 1080p?

ALT+ENTER does not solve the problem.:( Strange. So you don't have any clicking-problems in 4K after todays update?:huh: Would you mind testing my config.lua (the 4K one attached in my first post) to check if my file got corrupted somehow maybe?!:music_whistling:

I just did the latest update to DCS 2.5.3.21444 Open Beta. Seems that the clicking-problem in VR/4K is gone! Works as it should on my system again!:) Well done, ED! Thanks! :thumbup: But I figured out some other clicking-issue in 4K-non-VR mode and i've already created a thread on this issue, if anyone is interested... https://forums.eagle.ru/showthread.php?p=3623462#post3623462

I just did the latest OB update. (DCS 2.5.3.21444) After the update I tried to start DCS in 4K (3840x2160) and couldn't click anything on the main menu screen. I had to close DCS via TaskManager. Since I've got different config.lua files prepared (VR/HD/4K) I switched to the 1080p. Started DCS in 1080p and everything was clickable as it should be. Has anyone else expierienced this 4K-click-issue yet?! [ATTACH]193866[/ATTACH] (4K config.lua) [ATTACH]193867[/ATTACH] (1080p config.lua) (If anyone is interested in trying my settings, make sure to remove the ".HD" / ".4K" in the filenames to make the respective file work.) Edit: I'm not quite sure if I'm in the right forum section with this thread. please put this where it belongs in case I'm wrong. Thanks!