Sharpe_95

Hi everyone. Thanks for your feedback. If I am reading this correctly I belive the general answer is: 'Yes we probably will get the MFD 5/7.5nm scale once ED get round to putting it into the module'. Many thanks, -S

I have seen the same issue. I can't replicate it or find a reason for it though. Good luck getting to the bottom of this one dev team :-S

Thanks Newy. Great to hear from you again - hope you are well fella. -S

I have this. I noticed it at 7200 but agree it's there. +1

Hi everyone, I just wondered whether there was any intention for a 7.5/5nm scale for the F16 HSD (ie a level below the current 15/10nm scale)? I dont know if it simply hasn't been developed yet or if there will be no such scale as it is not present on the F16 model ED are making for us? -S

Yes I thought that may be the case but it doesnt seem right as even when the jet is accelerating the compass still tilts. I think it's worth one of the devs just having a quick glance to see if it is behaving as expected (doesnt do it in the FA18 for example). -S

As title - forgive poor explanation as I am not exactly 100% on the exact names of what I am talking about, however: When rolling the aircraft the SAI moves with the aircarft, however, the white arrow inside the dial (that pairs with the (static) roll degree markers outside of the dial) does not move. Seems like an error to me - sorry if this has been reported, is not an error or if the Dev team just hasn't got round to this yet. -S

As title really. It seems like as the thrust is advanced the magnetic compass tilts in the pitch axis (extremely in some cases) in relation to the thrust input. This is most notable in reheat/burner. I am not sure if this is supposed to do this or not? If it is supposed to do this, it seems to me that the pitch change is associated with the position of the thrust, not the relative g force imparted on the aircraft (nor the movement of the jet) - to that end it seems like perhaps this is in error? Sorry if this has been posted or is not an error or the dev team haven't got round to it yet. -S

Prior Post? Yes for other modules (most recent in May 2019) but with no fix. None specific to F16 that I could find, but IAH I cant search all 26 pages either - nothing in the first few though and nothing on a search for 'F16 Space/F16 spacebar'. Version: Open Beta 2.5.6.45915. OS: Win 10 (up to date). Issue: Space bar does not move lesson forward (as per directions) on F16 missions (note this has always been an issue for me and may not be limited to the F16). Have tested the error on all 8 currently available training missions. Same issue. Work around's tried: - Wait for Wags to stop talking without pressing anything (failed) - Check space bar not conflicting with other call backs (no issue, default key map being used, space only mapped to 2nd trigger detent). - Try pressing gun instead of space (fail). - Try having space mapped to no call back/inputs (fail). - Try mapping space to first gun stage (fail). - Try exiting and clicking 'fly again' (fail). - Try full exit of to main menu (fail). - Try full exit to desktop (fail). - Try system restart (fail). - Try full reinstall (not applicable, this is a new re-install as of two days ago, and the issue has been consistent with other aircraft for the last few years, despite multiple re-installs along the way).

Great, i get one day off to fly and this is what i am rewarded with thanks ED :doh:

Funny ha ha (especially when ejecting) - but is there a way to turn this off? I am new to F16 and want to practice landings and flying in general - this is prohibitive and I would rather not have to wait until the weekend when I next get to fly (this is wasting what little time i have available these days........).

G Speed/ToT Error Hi there, This was reported back in Feb here: https://forums.eagle.ru/showthread.php?t=232012 I wanted to add to this as I am experiencing the same thing, with an additional issue. In my case, along with seeing the same error that Razi saw I am also seeing the following: - HSI set to waypoint and auto selected with sequence (to show waypoint heading bugs in conjunction with flight path on HSI and automatic selecting of waypoints. What I am seeing in addition to Razis points, I have noticed that the selected target waypoint cycles to the next waypoint well before arriving at it (as much as 5nn before) when on all other waypoints it switches over at less than 0.5nm as I fly over and turn to the next waypoint. I think this may have something to do with why the GS/ToT is not working as it seems to think the waypoint is ahead of its actual position? - Hope this helps squash the bug. - Sharpe.

Hi all, I dare say this is an old error but i cant seem to solve it. In tutorials (FA18/F14 etc) the command to start the tutorial is 'press space bar' - however, this does nothing at all for me. Install is new and clean and to double check i tried a repair - no joy and the a full uninstall (delete of all files etc), still no joy. I dare say there is some kind of simple/obvious fix out there - but what is it? Thanks in advance, - Sharpe

I sympathise. I can't wait either. As I dare say the previous 6 pages may highlight the current rumour is 21st Dec, but that is just a rumour. For my part, I think some time early in the new year (possibly even 1st jan). My theory is that while the 21st would be a great time to release in terms of catching people for Christmas and people having a good amount of time spare to buy/download/install/set up/learn to fly the Cat I don't think (personal view) this is what heatblur will do. I think Heatblur (based on their commitment to excellence and the sheer hype behind this module) will not want to have a week or so of time when the aircraft is released but (with all the good will in the world) the inevitable bugs arrive but not have your team in place (being holiday season) to immediately start bug squashing. To say nothing of 'what if something really goes wrong' (like the downloader fails or people can't get it working en masse) and they can't fix it for several days over Xmas - they wouldn't want that to ruin it for everyone. From a business position (assuming it could release by 21st) I would hold release until the 1st/2nd/3rd Jan and then have my team in place (and rested) to start bug squashing as soon as the feedback comes in. I guess the only other window for release (assuming my line of logic is accurate) would be some time between now and Monday- which seems very unlikely. Either way I am sure it will be great and probably won't be that much longer. Quite frankly, I'd take it now, bugs or no bugs as I am sure a lot of people would. Happy hoping!

Hey guys. My wife is forcing me to get rid of my projector and my ubbutto gaming chair DCS setup. 2 questions: 1) How does dcs look on an ultra wide monitor? In my mind it would look rubbish & strange on such a wide but shallow aspect ratio but does anyone have one or know for sure? 2) Does anyone have any recommendations for a good gaming monitor that would be good with DCS - size is no issue and peice is broadly no issue. -NB: No VR suggestions please. I've made my peace with not getting that for now ;) Many thanks. - Sharpe

Yeah thats the 'top/upper' detente i am talking about. When I advance my throttle to that detente it should read 99/100% thrust but not be in afterburnet (this is with no curves set). Instead, it reads 94%.

Hi guys, For those that have the TMWH and use the front and back detentes I assume everyone has the same issue with the FA18 throttle?: With no curves set on the TMWH throttle axis, the back/lower detente works just fine (throttle is just before the idle cut off). However, the front/upper detente only allows about 94% fan speed before it hits the upper detente. In order to get the front/upper to detente to a point where it shows 99/100% fan speed (ie, before afterburner but not in afterburner) in the sim, I have to set a curve on the throttle axis of -16. This is highly undesirable as while it provides the correct range of movement on the throttle, it means that throttle inputs at the high and low end of the curve (ie low speed and high speed) are massively over sensitive. This is particularly annoying for AAR, landing and formation flying. Is this a bug, an 'FA18 in Alpha' thing or does ED consider this 'correct'? Given that over 50% of the DCS community appears to use the TMWH (according to the poll done by Wags regarding what types of HOTAS people use) is there any intention for ED to change the way the throttle is mapped to allow for the full range between the two detentes without the user having to set undesirable curve profiles?

Got M2 SSD so should be ok on the load times (its just slower than usual). Will uninstall the refresh/clean app immediately. How do you resolve the gremlins issues created that you mention?

[Win 10, most up to date version of dcs, gtx1080, 32gb ram - NOT using VR] Guys are there any good graphics or system troubleshooters out there? I think a graphics (or some other system/driver update) has totally ruined my game. It was working perfectly well until last night when I did a lot of PC driver and system updates. Now DCS is crashing a lot more than it was (it was faily stable before) and its taking even longer to load than usual. Critically in game where as it used to run smooth as silk, now the FPS is all over the place and the game is stuttering/catching every 2 to 3 seconds. Does anyone have a suggestion for how this could be fixed without needing to reinstall Windows? I tried a roll back to before all the system updates but it failed for some reason. So far I have tried repair and now a fresh install of dcs (I left my saved games file where it was as I assume there is nothing in this causing the issue). My gut feel is that this is not DCS (or if it is it's some graphics setting that needs to be changed either in the Nvidia settings or in DCS that has tripped up). I'm running a good pc with a 1080gtx and as I say dcs was working perfectly till yesterday. Only change was so lot of system refresh type stuff using a tool called Iobit. Any help out there? *Updated notes* This issue is only effecting DCS. I tried skyrim an it seems fine. The game now crashes every time I get into sim and pres 'esc' then 'quit' (hangs screen and fails to move). I have completely uninstalled the graphics card and reinstalled in - no change at all (although skyrim still running fine). - Sharpe

+1 - or just make the ball more visible? I understand people in VR can see it reasonably well so maybe it's something to do with non VR resolution or rendering? In my case I'm going to say it's not to do with screen size as I am on a projector. - S

Fixed- saw a response in another topic that resolved the issue. If you have this issue the fix is: - Set a -16 curve on your throttles. That's it, simple and effective fix :) - S

[ALREADY REPORTED] RWR to HUD glitch - stays on if pwr off RWR Hi guys, Sorry if this has been posted somewhere, posting in a rush before bed. First - thanks for the updated patch on the Hornet - good stuff :) I may have spotted a bug in the function of the RWR in relation to how it comes on (and off) the HUD. Steps followed: - I powered on the RWR. - I sent the RWR to the HUD. - I did some flying around. - I turned the RWR off (without first taking it off the HUD, assuming that powering off the RWR would do this anyway. However, the RWR threat symbology/lines stayed on the HUD even though the RWR was off. I turned the RWR back on, took the RWR off the HUD and then turned off the RWR and this fixed it. Sorry I can't remember what was locking me but I think it was long range air defence search radars. This was a multi player mission with about 8 aircraft in it. Map was Caucasus. - S

Hi Guys, I have a TMWH and I have noticed that with the detents in place (I like to have them in place) the thrust range (as indicated by the engine rpm) only goes to about 92/93% before the afterburner detents. In order to get full mil power without burner (100% but not in burner) I have to lift the throttle onto the stops and kinda balance the throttle at the edge of the detent. Two questions: 1) Is this right? I assume not as I would expect the detents to allow me to go to 100% and lifting over goes into the afterburners? 2) Assuming this is not correct (Or rather 'optimal') is there any way to recalibrate the sim/thrust range so that the thrust range goes to 100% on the stops and lifting over goes to after burner? Many thanks. - S

Hi guys, For those in the know regarding helios: I would like to build a very simplistic helios profile for the F-5E, just a couple of guages and switches. Does anyone know how I 'point' helios towards the F-5 (rather than say, the A10c or KA50? I can build the profile easily enough, I just dont know how to get helios to recognise the F-5E and DCS to recognise the helios profile for F-5E? As they are ultimately call backs, I am a little surprised that my A10c profile does not have some limited functionality for the F-5E (ie, the landing gear up/down/toggle keys are both the same - so you would have though that it would raise/lower the landing gear). Can anyone offer any advice? - Sharpe

Ok fair one, no argument. That said, my friends that also fly the A10 say they can see the HUD and down to the FPM dials from their seated position. My view still does not line up with what they see. Also, the posture of the 'pilot' (virtual) mean i have to keep messing around with TIR and/or sit uncomfortably just in order to see the jet. Surely this is not correct? -Sharpe