VampireNZ

Haha it's all gd BN - just giving you a hard time. I also totally agree with you - was interested in the Afghan map as well and considered the full terrain the better deal. Just saw a few issues with slow mesh/texture loading when I trialled it last week so just investigating before purchase. Shame Kola doesn't have a Trial either, as that would go well with the great new Viggen module I just bought - should have got it ages ago, awesome aircraft!

Oh it didn't happen on just the first flight, as I thought the same thing - it happened in a similar fashion on all my flights on the map. As I mentioned I don't experience it on any other map. As you say it might just be a thing with the 'newer' maps - as Syria would be my newest map, if you don't count Marianas WWII. But yes - def a deal breaker for me if that is the case unfortunately.

I recently downloaded the trial of the full terrain to try it out, having operated in the area. I noticed that when I checked out the F10 map, and then went back to cockpit the terrain mesh and textures would need to re-load, which they did very slowly - like over around 5 seconds or so? I don't have anything like this problem in any of my other terrains, so Caucasus, Syria, Nevada etc. Is this just because it was the trial version, or how this specific terrain behaves? Overtall I thought the terrain was very nice and very familiar - but not interested if I need for the terrain and textures to re-load every time I look at the map etc. EDIT: Oh and just a quick question - what is up with some of the airstrips?? Super wavy with a ski-jump in the middle? I noticed it with a few of the smaller airstrips - can't remember the names specifically but I did try to get a pic of one of them. Is this how they are actually designed to be - or still WIP? (I can't remember getting air time in the middle of a landing roll-out IRL)

Congrats on taking the opportunity...but generally when people are asking if something is worthy buying, they would usually like non-biased opinions of people not associated with the company selling the product.... Customer: "Hmmm Is it worth buying a Toyota Tundra?" Toyota Salesman: "Absolutely!"

Option in Target List, perhaps at bottom of list - to just go ahead and engage and kill ALL the targets you are looking at - if suitable weapon selected of course. Example - 10x chaps with AK47's identified and listed...Gun selected - George feel free to waste all of those dude holding AK47s. I really don't think I should have to go through the whole process of searching and then commanding George to engage EVERY single soldier seperately one after the other ten times. I would sort of expect a mildly competant CPG to engage and kill all those targets himself if he has consent to Free Fire. If you, for some reason, don't want to kill AK47 baddie #10 cause you feel bad for his kids or something - just disable the free fire and make weapons safe. Obviously only with suitable serlected weapon - so he doesn't kill AK47 baddies then start plinking away at the T-72 sitting beside them with his gun for eternity... I would also like to see George searching for targets at say the selected target WP or ACQ as well - as opposed to me trying to pinpoint it with my head and telling him to search....the target area we are specifically headin to to kill targets....so you would think he kinda would be looking at the area already... Apache is a pretty great module - if only the CPG would act more like a qualified CPG, not a school kid on Army Experience Day that you have to tell what to do every 2 mins.

+1

NOPE

As my initial thread regarding this was closed and locked by moderators stating - "So fixed internally, wait for it to release in an upcoming patch. Thanks." was not actually fixed, or released in the upcoming patch - I have re-opened the bug thread as it has not been 'solved' Refer to

& The main problem is not the horn - it is the fact Boost climbs FAR too quickly based on throttle position - i.e. you are only at 25% throttle position or slightly below (hence yes you get the annoying horn) but pulling +7 boost, which is completely ridiculous. Your RPM setting in the Mosquito is not determined by the silencing the gear warning horn - it is set by engine parameters/performance/longevity. My blue line graph above is even still a bit 'loose' on boost as further investigation revealed that you were even further into the throttle travel at +0 boost than the 28-ish % I show. So I re-iterate - it is NOT letting something as 'simple as the gear horn interfere with your enjoyment" - yes I know that is the OP, but that is just a nasty by-product of completely fantastical throttle/boost/engine mapping characteristics of the DCS Mosquito at the moment, that yes is hampering the enjoyment of this product I purchased somewhat. If I wanted arcade fantasy simulation I could play a different arcade flight sim. Could it be fixed - of course.....we shall see.

He actually says "30 inches of boost" - which is actually +0 lbs boost on the gauge, which is about 30 inches of mercury or one atmosphere (29.92inhg). So he just used the inches figure instead of the pounds figure for boost we are used to. He also doesn't say anything even close to "Start at 0 then increase to +13 boost for a straight T/O". Regarding weight - they usually don't fly with 10% fuel either, which is what I used and nil stores at all. So just a bit of extra radio gear maybe, but most restored aircraft have this stuff installed for historic reasons. It obviously has the cannons installed etc. - again I used nil gun ammo. FYI it is not a 'Museum' aircraft either. Also, may I ask why you thought it necessary to post a link to my profile?

Refer to notes from this pilot flying a restored FB26 with RR Merlin 25 engines installed. (Canadian version of the Mk. 6) Takeoff - Keith mentions he takes off at 0 Boost for a smooth straight takeoff. Try that in DCS and you will be lucky to see over 100 MPH! Cruise - Their usual cruise settings are +4 Boost @ 2400rpm = 260mph cruise. Again, try that in DCS at a low level cruise +4 @ 2400rpm and you will get 235mph cruise...+ warning horn constantly. Also he notes they don't take her over +13 boost, and later mentions this is good for 320mph. Again - DCS +13 will get you 295mph at most. 30 mph might not sound like a huge amount, but the Mozzie seems to be really struggling to see the performance or speed it was famous for. Would be really nice if she got a tune-up at some point. Would be nice to see her getting along at the 300+ in high-boost cruise like she is supposed to.

ED do seem to have nailed the actual Mozzie manual well in that "The undercarriage warning horn sounds when the main wheels are not locked down and the throttles are less than 1/4 open" - as using the VKB config software my throttles are outputting exactly 25.0% at the warning horn (note it must be BOTH throttles at 1/4 or below to sound horn). However, there definitely seems to be something funky going on with how much boost is being applied at low throttle openings! Watching the formation flying of of Mozzie KA114 fitted with Merlin 25 engines in Auckland and you can catch a glimpse of the boost gauges sitting around 0 lb boost and he is just dropping in and out of the horn with the throttle pretty much stood up - prob dropping into the negative boost area to slow it up now and then. (non-historic boost gauges but 0 lb boost is still at 12'oclock.) He looks to be flying around 180 MPH - but don't know if he has a little flap out or not - prob not. Doesn't really matter as it is more the throttle postion to boost output ratio that is the problem, not how much power it has.....that's for another post lol. But definitely not sitting up at 7 lb and dropping in and out of the horn as we are in DCS! Something else quite strange is how there is no manifold change or effect on the engine at all during flight in the DCS Mozzie for the first 1/2" or so of throttle travel. then it jumps up to 0..then races around to 8 at very low throttle settings? This would definitely have an adverse effect and also indicate that the throttle/boost curve is not quite right. I have attached the ref vids below - first one is quite dark so only catch a glimpse of the settings, but it is stable flight the whole time as he is in formation. Second vid is in same aircraft with much better view of gauges. Interesting to watch the takeoff and how the manifold pressure reacts at certain throttle settings. Also interestinig to note in second vid he is flying around at -1 boost at around 180 MPH - no warning horn. EDIT: Was also thinking this could be related to why the DCS Mossie throttle stops are located at +14 lbs, instead of the actual figure for the Merlin 25 of +12 lbs. Further to the above - I have also included the boost curve info for reference/comparison purposes. Firstly some information from the Merlin engine manual regarding the PROGRESSIVE boost cam. Below is what I would consider a reasonable boost/throttle position progressive curve that more closely matches what can been seen in in-flight videos of the Mosquito - I note this is not specifically based on any info as I have been unable to find any. However, you will note it is a lot more likely example of a PROGRESSIVE boost curve than that shown in the second graph in red - which is what we currently have in DCS. All figures taken from a Mosquito at Channel map at 1,000'. I think most people would agree the Blue curve would be much more likely than the Red curve for a progressive relationship between throttle position and boost - and would also enable lower power settings that don't require the throttles to be below 25%. I specifically note the settings for 0 lb boost as seen in one of my ref videos just skirting the upper limit of the 25% mark. I realise the Mosquito doesn't really get any attention regarding development any more - but as a Kiwi I feel it is my obligation to try and fix her up lol. I understand ED may not have the available manpower to address the issues with the Mozzie and would happily change the values myself if ED would point me in the right direction.

Just a few small bugs - regarding the ASI needle unpainted tail - in all ASI's of that era I have ever seen in RL or pictures, the tail is painted matte black for obvious reasons. Pics of Spitfire gauges/needles included for reference. ED may have referenced an aircraft with a replacement unpainted tail - all good. Any chance we could paint it? Also regarding the ASI face - firstly the wording is incorrect - it should say TENS of MPH, not TEMP of MPH. Also the face is very cluttered - if this was installed in the reference aircraft then all good, however I have also attached below an actual ASI pic from a Mosquito for ref. I have modified these two issues myself for now and placed the mod in the User Files section here - https://www.digitalcombatsimulator.com/en/files/3343182/ Video of gauge in cockpit here -

It is fairly well known that the AI are Aliens flying soopa-powerful versions of our aircraft. Generally the way around it to fight equal performance aircraft is to load them up with drop tanks etc. and disable jettison in the ME.

Awesome that ED have included such detailed missions included with the aircraft! As a Kiwi it's a bit of a shame you can't fly in the 487 SQN aircraft.

That's so cunning you could pin a tail on it and call it a weasel!

Come across this thread as am setting up throttle detent on the VKB STECS - for what it's worth noting there seems to be be several sources for Merlin 25 engines stating different settings. This one seems the lastest amendment level. In any case I have set my detent at +12 lbs, as per the asctual aircraft setting and provides a nice reference for 'power' settings at and above it, along with +12 being the required 'clearing' power setting. Just drop below the detent for continual power settings. I might just get in touch with the guys up in Ardmore building the things and ask them. (I have also added to this post instead of starting a new one, so the above previous info is included for ref - I would be interested to see where ED got +14 from for the stops on the 25?) EDIT: This also likely to be related to the issues surrounding the boost/throttle position curve etc. Have provided some info in this thread -

> Double checks he is reading the F-14 forum section...not the F-4 by some random click error lol.

Hmmm - all my years as an aircraft engineer and we lockwired fasteners so the fasteners didn't vibrate loose and fall out....not to retain the odd button that was lucky enough to be under the path of the lockwire lol.

Pretty pointless trying to rely on Auto Handoff in the Viper the way it is currently - the best you can hope for is it gets the Mav seeker close then you still have to manually slew the mav seeker to the tgt - using the overly-sensitive maverick slew controls

Hi Brad - sry but it seems that is not quite correct. As I am unable to post anything from actual manuals - suffice to say there may be an Operational Check with the aircraft jacked to turn the tailwheel to the side, and check if it returns to centerline when let go. If it does not - it might refer you to another paragraph to fault find why the TW isn't returning to center by itself with aircraft in the air.

Thanks for taking the time to explain english to someone who has been speaking it for 50 years. English may not be your first language, but I see you are taking the time to learn patronising sarcasm, please correct me if I am wrong. Coming from an aircrew and aircraft maintenance background, if I told the Captain of our aircraft after he informed me of a current fault that "it had been fixed in October"...I can guarantee the answer would have been along the lines of 'Congratulations, do you want a cookie or something? It's broken now as I have just told you - would you mind doing something about it" But obviously we can't respond like that in the real world. So sorry - was just a bit confused at your response. Several examples of how it is 'currently' broken, and the response from the ED side of things is how it 'had' been fixed. Um ok - well now it is broken again. Maybe something lost in translation, and no I am not barking up anything...just trying to help by adding some more info. I apologise.

LMAO - if I had made the post above, within minutes someone would have jumped down my throat and moaned about 'necro'ing a 3 year old forum thread...and the Mods would have immediately moved it to the Liveries/Skinning > F-16C section! Both these things literally have happened to me in the past few weeks - I feel special

Noticed a small issue with SSA and the JetSeat. After taking off the Ground Bumps and Ground Roll effects continue while flying. Happened so far in Viper and Apache. The effects are quite strong as I assume it is taking your speed into consideration? I can stop it by unchecking the appropriate boxes in the Effect Settings list, but will start again when re-enabled. So I just close SSA and re-open it entirely in flight and it works fine again. Is quite rare it happens and not sure what might be causing it - just normal takeoffs. Using Ver. 2.9.0.0.

Sorry - but did you not see the screenshot I just took and posted above with CPU Core 3 maxed out for the entire duration DCS is open after loading an aircraft?? Disable then re-enable Affinity and it stops maxing out. This side-stepping/ignoring of faults/problems in DCS is getting a little out of control?