SQINTO

I have been trying to create a set of rocket depression tables for the Mosquito and as part of this I have been checking that my theoretical model matches the DCS rocket performance. In doing this I found some odd things so looked in more detail. I used TacView to finely examine the rocket speeds from they leave the aircraft to to target (TacView attached - I can't find the original Track file). This give a very odd speed profile as shown below: The rockets jump in speed for that of the aircraft (shown just before t=0). Speed then increases but falls off indicative of rocket motor exhaustion. However, norte that all references point to a motor burn time of 1.5 - 1.6 seconds. At about 1.0 seconds the speed instantaneously drops by 80 mph then increases again before falling off. As you can see this is consistent with 3 launches on the same mission (Channel map rocket training mission). Extracted data is in the spreadsheet attached. I have not checked rockets on any other module. Mosquito Rocket Speed.ods Tacview-20211223-180509-DCS-Mosquito FB VI-TRG-Channel-RP-3 Instruction.zip.acmi

I have found the fiollowing issues with the controls for the Viggen (moderate) and the Mosquito (critical) on the Marianas Map. These issues do not exist on the other maps and so I conclude they are a marianas map issue: Viggen: Unable change the setting on the primary altimeter. Direct clicking with a mouse, mapped HOTAS control or keyboard could change the settings. It is posible to change this on the Standby Altimeter normally; Mosquito: There appears to be a swapping of inputs. The axis on my throttle which controls pitch operates the rudder and a mini-joystick on the throttle moves the primary controls. Checking the Adjust Controls tab shows that these are mapped correctly (pirch control shows as pitch, etc.) and remapping them makes no difference. I have tried restarting the computer and repairing my DCS (Open beta) with neither fixing the problem. I have not tested other aircraft on the map so I don't know if the issue is limited to the Mosquito and Viggen.

Bomb depression tables and some suggested attack profiles have now been published. They can be found here: https://www.digitalcombatsimulator.com/en/files/3319264/ Many thanks to the people who have provided feedback. Further feedback is very welcome. TAW-Prof

@No1sonuk Yes, and that's the point of the request. To mark targets for others.

Would it be possible to add target marker ordnance? I note that the British did have flare and phosporus (smoke) rockets. I would be surprised if the Mosquito did not also carry some form of marker "bombs", but I have not found any evidence of this (yet). Thamnks and keep up the good work - I'm loving the Mossie

The technique that I use (not the "approved" way of doing it) is to line up then full brakes. Runup to take-off power on th brakes. Let go and some initial light tweakes on the brakes to straighten if needed. Once at a decent speed the rudder becomes usable and then use that. I find that powering up on the brakes helps minimise the swing. I've also applied curvature (33) on my rudder (though I use a Virpil Alpha grip with twist for rudder - actual pedals may need other settings). Hope this helps

I am working on a set of bomb depression tables, in the absence of anything anywhere else (if someone has already done this please let me know!). As part of this I was wondering if anyone knows the angular size of the gun reticle and/or the angular distance between the inside edges of the vertical bars/gap. It appears that the reticle is about 10-12 degrees but does anyone have a better measure? Is there anything thing else about the sight that I should need to know? I assume that it is mounted on the longitudinal axis but is is offset and by how much? Thanks for the help.

Found those after posting this - sorry

Whilst flying in VR I managed to damage myself with too low a bomb drop. This entailed me trying to use the Emergency Hydraulic Pump to lower the undercarage. This is extremely difficult in VR as you have to be looking directly at the pump handle to be able to operate it. In reality I'd expect the polit would be able to simply reach this down the side of his seat. With this in mind, would it be possible assign this to 2 keyboard mappings (pump up/down). This would mean that it could be done without having to look down at the pump itself. Thanks

Due to the difficulty in achieving a perfect trim for the aircraft it is very difficult/imposisblle to switch to the Nav seat to spend time settingup and operating the radio without crashing. To do this solo would it be possible to implement a simple (auto)pilot, to replicate a real polit, to allow for usage of the radio etc from the Nav seat? This would just have to be able to perform do an Attitude or Altitude hold (with heading hold as well if bank angle small - all similar to the JF-17 or Viggen). Perhaps this could come on automatically when changing to the 2nd crew seat whilst in the air - change to 2nd seat and aircraft holds attitude and possibly heading. Thanks

Can I put in a request to the fantasticv people who develop skins. Is it possible to create one for MS993 (N). This was a 617 Sqn (RAF) aircraft flown by Leonard Cheshire VC, whcih was used this for pathfinding purposes. His achievements are too numerous to mention here but please read: http://www.dambusters.org.uk/war-personalities/leaders/geoffrey-leonard-cheshire/ This is quite personal for me as I live where his first nursing home was created, it is/was in my front garden!

Disabled vJoystick (only keyboard, Mouse, joystick and throttle). Now works, though pitch trim is very sensitive.

I think I missposted this on the wrong forum: Posting here so that it can be icked up.

I am using a Virpil Alpha stick and MangoosT-50 cm2. Trim bound directly (not via keyboard buttons) to Flight Control/Trim xxx

Flying in VR (Reverb G2) I find that the trim has no effect. I can trim full up/down nose trim with no change. Normal cruise is slightly nose down stick irrespective of trim settings. Similarly rudder and aileron trim don't appear to have any effect either. Indicators move but no change in stick force. Trim controls bound to HOTAS 4 way and slider (rudder).

Left and high for me. Also, while there is a seat height lever there's no way to adjust the seat height. The Gun Sight Illumination switch does not move me in line. This means that I have to lean down and right to see through the sight.

Could you please add a keyboard bind for insert/eject the DTC cartridge. There is one on the Viggen (which also needs a data cartridge) which I find very useful. Many thanks

Everytime I start a mission in the JF-17 (whether in the air or on the ground) I always have rudder full left. As soon as I touch the rudder controls this corrects itself. I am using a Virpil Alpha joystick (twist for rudder). I'm not having this problem with any of my other modules (Viggen, Mig-21, BF-109). Thanks

I've had problems, though not a bad as yours, as I had lots of key bindings mapped to HOTAS switches via Joystick Gremlin. This caused some funny things to happen - like self deploying airbrakes. This problem seems to have disappeared/lessened when I reduced the number of "keyboard" entries generated by the HOTAS. I suspect that there is some sort of keyboard buffer which can get confused and swap keystrokes. Try mapping more things directly in DCS rather than via third party software and see if that helps. BTW Also G2 but Virpil and Joystick Gremlin

Unlike ships, oil and gas rigs seem to be invisible on radar, at least for the Viggen. Given their size and lots of angle Iorn they should be at least as visible on radar as a large shipo and arugably vissible from a farther distance due to the longer radar horizion caused by their height.