flybull

I too experience lower frame rates (VR) with the F-14 when compared with other modules (Hornet/Viper). Ive been accepting that as a price to enjoy this magnificent rendition, but would STRONGLY prefer better performance, (and a fresher looking, easier to read in VR cockpit!)

I noticed this described behaviour BEFORE the previous update.

Gday Ugra Team. It looks like you have done a stellar job on the Syria Map. A few days ago - there was a youtuble clip posted that show Ramat David At precisely 1:19 in that video, a hangar complex is shown. In reality it is a major HAS complex belonging to one of the 2 F-16 Squadrons at the base (117 First Jet, at least until they disband) I appreciate that detailed imagery is difficult to come by, however this video below, combined with Google Maps/Earth could be used to re-create this area. It is a MAJOR feature on the airbase. Also missing is the 117SQN buildings, situated off the flight line on the east side of the field, just north of the sun shelters. Hopefully you can add the HAS complex in at least. Thank you Dave

Hey OP, Don't worry about those dudes who are raining on your parade. I get your excitement. Wags let out a hint that we might get an Apache one day, and that was news to YOU. Im hanging for more western helicopters too. You're entitled to post - and nobody is forced to click your thread if they dont want to read it. I wish this community was more tolerant. All the best to you and dont be disheartened. I hadn't heard the tidbit until I read your post, so thanks. Dave

I saw that thread, but the point about the index pointers was a thread drift and NOT specifically acknowledged by a member of the HB team. Thank you.

Hello Team, With regard to the 2 speed index pointers on the ASI, there is a bug in that BOTH of them move with Mach. Per documentation, including your own manual, one of these index pointers should be fixed to IAS. Is this a bug you're aware of? Is it planned to be fixed? Before dudes jump down my throat about flying AOA on approach - the IAS bug is also used for Take off. Thank you kindly, Dave

Thank you for the reply. I look forward to reading what Cobra thinks. Kind regards, Dave

Hello Heatblur Team, May I first start off by congratulating you on the masterpiece that you created with the F-14. In over 35 years of flight simulation, I have experience awe at many releases that were great for their time. The F-14 is simply the best ever. Thank you. Regarding Heatblur "Forge" - a workflow introduced to us in your Pre-Order/Gameplay reveal trailer from OCT 2018, you advertised dynamic cockpits - including weathering changes and even different seat cushions. I would like to know what Heatblur's intentions are with respect to implementing these features. Cockpit weathering is particularly important to may users - I know that i'm not alone in wanting a fresher cockpit option - with the added benefit of assisting VR readability. There have been other discussions which have covered individual's preference - and I don't want this this to degenerate into a debate - I just want to know if/when we will get the advertised features of 'Forge" Keep up the stellar work. I'm really looking forward to the -A model (with a fresher 70s/80s feel!) Cheers, HEATBLUR Fan boy and F-14 aficionado Dave

Ourorbourus - you are just plain wrong. PAPI/ VASI completely different OLS. OP - +1. Lunatics comment accurate.

+1

Thanks for the tip....Ran it as advertised. Using the latest beta with a 1080Ti/M.2 SSD spec box. In places where I would normally experience greater than 27FPS, it was a noticable degradation of quality for me. Thanks for posting your findings, I wish ED would optimise the sim for us

Sublime..... Me: View public profile MENU: User Lists... MENU: Add to ignore list.. MENU: Are you sure? ME: F%^K YES!!!!!!!! Ahhhhh, the serenity. Good work gents for being so helpful, patient and professional. I admire you.

I would like to echo Kev2go's comments. A Block II E model (lot 26 or later) would be a fantastic opportunity for ED to make $.... With TG II approaching, its the jet "everybody" is going to want (well lots of people). What id give for an F model option .Even just external model allowing front seat only to be occupied. What i'm praying for - is that ED are secretly balls deep in the Rhino development, and that the first we officially know of it is when they announce its release as a complete module. (ideally completing the existing Chuck Lot 20 1st).

Hello ED Team. May I offer a voice of reason? It is obvious that the user base is passionate. Only a small proportion are vocal. This vocal minority DO represent a fair cross section of the community. The "Open Beta" moniker is probably to blame for some issues. it IS the default release version, and it costs the full amount. The "Early Release" (within Open Beta!) model causes HUGE frustration. I understand that your financial model benefits from it. If you are to keep operating on this basis - then there needs to be clear communication AT THE START, as to what will be included in the Final Release. Obviously bug fixes, should continue, but the all FEATURES advertised for the product should be included, before the module is finally released. I would prefer to not see "Early Access" modules EVER. Changing the definition of early access - and making contradicting claims (ie conforming to STEAM's definitions) will cause anger and frustration. Announcing developmental delays (on day of expected release, per SC) will cause anger and frustration. Anger and frustration is felt, because there are many other underlying issues (as other members have explained). It is a built up feeling. Specifically WRT F/A-18: Accept that the module is in EA until you deliver what was promised. Prioritise the outstanding items NOT by ease of implementation, but by importance to the simulation. My suggestion: Focus on NATOPS stuff first. Aircraft Systems, Flight Model etc. Then focus on Aircraft Weapons Systems, lastly - add weapons, stores... Implement the long-made promises to core simulation. Vulkan anyone? Don't tell us what's this weeks roadmap is. SHOW us by releasing something that is complete. ED - you DO have a credibility issue. Im sorry to call it out. Please don't announce/release any new modules until you have fixed, completed, implemented all your previous promises. When you're ready to release something new - please dont make it "EA" After you have built up good faith with your user base - you could then revert to the "EA" model if you insist. This can only be done with a community that trusts you - which it doesn't. I understand this may be felt as very critical - I cant apologise for being direct. MICROPROSE might be looking at some of your customer base - time to shape up. Thank you PS: May your next (fully complete) offering be an F/A-18E

In RL, The ball call is a hell of a lot easier to accomplish than in the sim. I suggest 3 options: 1: Auto comms, based on the sim detecting where you are in the pattern, weather or not ball is visible. 2: Abbreviated - where activation of a function key or HOTAS binding will initiate the relevant comm 3: Existing method - using menus/VA etc. Personally id always use 1 or 2....

I give up. ED!........

Someone at ED will understand the request and it will be judged on its merits. A considerable part of my wish was having the aircraft setup, ready to trap - so you don't have to make 15 selections on the fly. The current "QuickStart" requires you set the following items: Hook down Hook bypass - Carrier Anti skid off Dispenser off Harness locked Tune TACAN. Select HUD TACAN on HSI Adjust HSI range 10 and course set RADALT set L DDI page to Checklist or HUD R DDI to FLCS This should ALL be done way before the initial. You can do a Case III, or a full Case 1 if you wish - that will obviously still be important. I just want to focus on the last 30 secs or so, with the aircraft and systems all set up. Having a textbook "Groove" position pre set would help ingraining the correct picture for a 15-18 sec groove. Last time I checked this was the "Wishlist" thread...and I just made a suggestion. If you don't agree, at least read and understand what is being said, and offer something constructive.

Raisuli, one last addition. If you're focussed on realism, the dirty up is done in the level break after S/B retraction, not on "downwind". The start point you describe doesn't correlate to RL procedures. My "180" suggestion would be better. Maybe just before the "180" if one prefers to gather themselves after release.

In my suggestion - ALL those things should be already set up. That was one of the main points. If the A/C is trimmed and throttle set close to correctly, you should be GTG. Could potentially be doing a trap-a-minute. Ball-flying skills would ^. Let's leave it to ED to determine whether the request has merit and is feasible. I'm sure some users would love it.

G'day team, I was thinking that a QuickStart mission setting you up at the optimal 15-18sec groove, on the ball, on AOA, would be a great way of practising "ball" flying repeatedly. I would still keep the other quick start options, to perform the break etc. Other options like "180" and " 90" would give quick and easy start points too for practice. I would recommend having the aircraft already configured and set up - not like the current QuickStart, which has just about everything in the aircraft set up incorrectly - hook up, field landing, antiskid on, master arm on, dispenser on, harness unlocked, TACAN not tuned or selected on HUD, etc.... Can we have an easier way to shoot approaches? Thank you so much - feeling primed for Supercarrier! Cheers

There is often a frame rate reduction with the F/A-18C when landing on runways and decelerating. I noticed this at 80KTS before the last update, now it seems to be 50KTS. Predominantly tested on NTTR Quick start missions. My suspicions is that it has something to do with the ground friction algorithm - perhaps to stop deck sliding. This is NOT an issue with AI or static aircraft.

The gear lever works like a 1 arm bandit

Instant Action F/A-18 Nevada Free Flight. select gear down - poker machine on L DDI :-))

Running DCS with RIFT S. I’ve been experiencing an FPS drop after landing and decelerating below approx 80 kts. I get a steady 40 FPS until that point at which my frames halve. Updated to latest build today - problem still exists I ve been testing F/A-18C instant action, Nevada “free flight” and landing at Creech. There are no AI assets etc.

Amen!