Hawkeye_UK

Hey reflected i only purchased the campaign because i have played your other excellent campaigns and wanted to support the project. I bought in when it came out knowing it would be one of those to wait for the map to catch up re VR. Agree with your thought process also, and purchased with the foresight that they cannot leave the map in its current format. So much detail just not needed for flying along, just really hoping for ED to optimise in a sensible matter over the next year or so, fingers crossed. I think they will have to do something as you only have to look at the lack of uptake for MP on this map tells you there is a problem with it, which is a shame as you say as it is stunning, just not all that detial actually adds to it over fps!

Yea ive pulled all mine out to a separate one drive so can have them on an ipad and sync at ease. Point is we are getting alot of new players to DCS that do not even know their is a manual for the module i kid you not! Using chucks guides which are excellent but do not cover everything. They just need to be highlighted, i do think it should be on the email purchase as a link but also in the aircraft folder on the start screen too (along with instant action etc). Its just that way more people might actually read them too "

Yea totally agree with this, my earlier comment was a bit brief and not very helpful in hindsight just saying GPU but that;s what i meant - expecting too much. I hate to be the bearer of bad news to the original OP but realistically your card is real borderline id say for DCS, its just so damn demanding. I have a similar system re 2080ti and for me in VR the channel map is by far the most demanding of any map we have. All the others including Syria run far far better. I have no idea what the reason is for this but given that a 2080ti is as of 5 months ago the best card you could get it i just feel like something is wrong with this map. Needs real optimization or something. Something somewher isnt right though as i think Syria is just as detailed, if not more so and that runs far far better on a much bigger map. I was hoping it was going to be like the Normandy map that came out, had issues , got optimized and now runs really smooth. To note i think its the main reason why no one uses the channel map its just not feasible by any stretch MP wise with complexities thrown in. I was surpirsed to read on one of the news letters that basically the map was nearly finished. For me its my only module i do not get any joy out of or value (i own everything except Christian Eagle and Yak). FIngers crossed they find some time later in the year to sort out and revisit and its a great potential but in its current format i just can not see it working (Perhaps a 3080/3090 not that you can buy them)! Edit - i suspect it might be the building texture detail - think they went a bit overboard as cannot see indivdual bricks at 300 mph etc but the level of detail if say in CA is unreal! As i said think it needs a total rework / revist of what is causing the problem as its a shame as reflected has made a great campaign but in VR the base map just is too much before adding the scripting ontop.

Rudder, rudder and more rudder. Cannot underline that enough. The model is good though as it gives you so much feedback its better than other non FBW in that context. Good rudder pedals help enormously for fine control and slow speed turning flight / fight and gun snapshots. To this effect cannot recommend MFG Crosswinds enough. They are not the cheapest, or the most expensive but they are sure tough to beat and a solid investment if this is a main hobby. Mine are well over 3 years old, as good as the day i bought them, do not degrade, solid build, adjustable and also excellently designed if you switch planes alot (i use the choppers alot so being able to switch instantly to a non spring return centre is a huge benefit). Alas it has to be said that hardware does indeed really help once you get away from the FBW modules, along with a good quality stick input. Its the same as the warbirds.

Update - notice since the last time i looked the documentation has indeed been updated recently with more manuals - which is excellent although it could be laid out much better re sections and also needs completing as some are missing. But it does need highlighting futher, i'd actually strip this out of the downloads section and have a totally separate column called aircraft manuals as a main link header next to Support. Honestly being a regular on one of the main PvP servers its amazing the amount of new DCS players that do not know how to find the manuals or aware of their existence even.

What is needed is counter battery fire systems for the opposing team to retaliate. It would actually make artiliary more relevant as at present it is way to OP. Also the fire sequence for some reason can cause slow downs in performance this needs to be reviewed (as in stutters in MP for those not even within view distance).

ED, It's come to my attention alot of new players to DCS are actually unaware of the location of the aircraft manual by ED or the third party. It is currently buried in the file structure of the install, far from ideal. This is something that is currently poorly implemented if we are being honest. The downloads section on the website contains a token fraction of available manuals and are not always current. Can we update this part of the website so that all modules, including all third parties are easily accessible for reference. Ideally you would click in there and have 4 sections. Jets, Helicopters, Warbirds and a General game section covering the game manual, combined arms etc. Its literally an hours work top"s for one of your website guys. When purchasing a module on the confirmation email it should contain a direct link to the manual on the website. Please can we come up with a better structure than what we currently provide new players. Many thanks.

Please can we fix the SA19 Tungusta missile. Alas on public servers it is being used often innappropriately to kill MBT's in combined arms. The point is there is no way this system should be killing tanks with the rocket warhead, AP its not. Also the main AA guns will shred tanks in seconds, HE shells are causing huge damage. Which also brings me onto another issue of HE rounds in tanks being able to kill other tanks. Both issues need to be resolved please. Track file attached , the Tungusta is a priority however. SA19 armour killing.trkSA19 armour killing with he guns.trk

Excellent thank you - i had missed the keybind - amazing given that i fly and use all aspects of the Viggen including nav computer TOT etc lol. I have had a break from the module for the last year and it only really became an issue with the 2.5.6 update. Thank you both Machelot and also Jediteo, one for the solution and the other for the fix - both greatly appreciated.

One of the features of the Viggen module that i have always loved is the Radar scope and the mission planning for strike sorties which require INS fix points. It seems that for quite a long time (think since 2.5.6) the Radar scope at night is unreadable, especially bad in VR. I can play around with the brightness and gain settings up and down however cannot get a clear picture due to the stupid baked on reflections (incidentally which dont seem to go up and down with the brightness). Can as a short term fix remove the horrible baked in reflection so we can actually see the scope. Making out anyting on the scope now at night is impossible for targeting, same goes for INS fix updates. Makes the Viggen now a day only fighter - needs resolution PLEASE (not complaining but a year on it needs resolving). Many thanks,

Guys update to v 27, things are certianly getting better. The largest cause of link being lost is the F10 page in VR> i do wonder if this is related to the age old memory leak that has never been resolved. Have you Oculus controller handy at all times and as soon as you get the disconnect of the link, click in quick actions in the headset to renable the link and 95% of the time you will get back in the game. Also to note for the Quest 2 - run an autoexec file in your save game config folder with these line's; no_device_hotplug = true options.graphics.stereo_mode_use_shared_parser = true disable_write_track = true Bascially it stops USB hotplug isses, Diables track writing (optional but it can help) and the main one is the middle line. This will give a good boost however note it is beta. It will also stop some annoying issues such as clouds in one eye and not the other however it will introduce other issues such as at nighttime with cockpit flood lighting only showing in the right eye. ED really need to put some time into Quest 2 given that its now the largest VR headset by type.

Have they altered the flight model? If so, why once again are the changelogs so poor, its an old complaint i know however they really must sort out their communication. As per FM i noticed few patches ago the L39 got "adjusted" for the worse and not one mention of it in the notes. From a wider persepctive frankly the amount of changes that occur that never make it to the release notes can be frustrating. It does become tiresome especially when some of these changes affect ME and third party mission designs.

GPU

Excellent thanks for the update - hopefully this can make it into the OB as its a really immersion killer in VR

In the Interim check out https://www.mudspike.com/chucks-guides-dcs-a-10c-warthog/ This is updated for the new A10C 2 and has the updated Hotas controls. Also from the ED website, check out kneeboard pages. https://www.digitalcombatsimulator.com/en/files/3313817/ Also this is excellent as a quick check, https://www.digitalcombatsimulator.com/en/files/3312541/ Appreciate the OP post of how important manuals are and confident ED will deliver but in the interim id recommend using these. Lastly have fun with the A10, its an excellent module to invest time in. PS - i'd also recommend running OB - the reason being is stable is not bug free and you get fixed quicker on OB, also next month will see the 2.7 release with the eagerly awaited weather updates.

More to the point can we have an update from ED on when this is going to have an actual dev fix - needs to be an option in settings please. Cleary its easy to do - why the near year wait - has it been forgot?

Ok so i have an ongoing log with Oculus Support and will provide feedback as i hear back. I also would like to clarify has anything changed with the way ED handle the flow from Mission editor, cockpit, to F10 map in either the Hotfix/end of Jan Feb patch. This started for me two weeks ago. It happens both in SP and MP. I can replicate it now 100% of the time on say mission editor where build a mission, click play and when you get to the choose slot screen and select one, you briefly see the aircraft loading in for a milisecond before it crashes back to the Oculus home within the headset. It looks as if on the monitor the game is still running. I do not understand however why despite showing the fly screen (as in stationary image and not yet pushed the fly button an i7 9700k core is maxed at 100%?). 95% if not more in MP if i say choose tac command or jtac to look at the F10 map, or even inflight checking the F10 map will dump the link. To note there is a long standing F10 map issue with this that causes FPS loss anyway. This for me has made DCS and Quest 2 completely unflyable, especially when associated with the FPS drop in game that sometimes can be corrected by al tabbing to another app and back in. Checking in the Oculus logs i get his every time there is a disconnect. Service_2021-02-19_17.32.16.txt] 19/02 20:07:28.851 {!ERROR!} [xrstreaming] WinUsb_ReadPipe(handle:0x000001D27A1A7610, ep:129, len:1024) failed: (433) A device which does not exist was specified. {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [xrstreaming] WinUsb_WritePipe(handle:0x0000000000000000, ep:255, len:4096) failed: (995) The I/O operation has been aborted because of either a thread exit or an application request. {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [xrstreaming] RemoteHeadphones: pipeCallback: sendAudio() failed to send audio buffer: -1002 {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [RemoteHeadset] Error getting user settings from session. Result=-1002. {!ERROR!} [RemoteHeadset] Error getting audioControlfrom session. Result=-1002. {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [RemoteHeadset] Error getting hands from session. Result=-1002. {!ERROR!} [RemoteHeadset] Error getting hand skeleton data chunk from session. Result=-1002. {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [RemoteHeadset] Error getting tracking from session. Result=-1002. {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [RemoteHeadset] Error getting body from session. Result=-1002. {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic 9 {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic {!ERROR!} [xrstreaming] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic {!ERROR!} [xrstreaming] inbound data processing loop exited: I/O error (13) {!ERROR!} [Kernel:Error] OVR Error: [Service_2021-02-19_17.32.16.txt] 19/02 20:07:29.199 {!ERROR!} [xrstreaming] Failed to parse PCI vid and pid from string "" {!ERROR!} [xrstreaming] Failed to parse PCI vid and pid from string "" {!ERROR!} [xrstreaming] Failed to construct channel for winusb,2833,ff,89 {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [DisplayManager] [DisplayManager] Failed to set power profile. {!ERROR!} [xrstreaming] Failed to construct channel for winusb,2833,ff,89 {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [Kernel:Error] [Aggregated 24 times] OVR Error: {!ERROR!} [xrstreaming] [Aggregated 20 times] Reference to topic is NULL in enum XrspResult __cdecl XrspTopicClose(struct XrspTopic *): topic {!ERROR!} [DisplayManager] [DisplayManager] Failed to set power profile. {!ERROR!} [MobileConfigWrapper] getBool() received invalid param: oculus_store:is_rift_redesign_enabled {!ERROR!} [MobileConfigWrapper] getBool() received invalid param: oculus_store:is_rift_redesign_enabled {!ERROR!} [MobileConfigWrapper] getBool() received invalid param: oculus_store:is_rift_redesign_enabled {!ERROR!} [LifeCycle] Leave VR with unregistered pid: 2864 (Unknown) {!ERROR!} [xrstreaming] WinUsb_ReadPipe(handle:0x0000000000000000, ep:255, len:1024) failed: (995) The I/O operation has been aborted because of either a thread exit or an application request. {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [xrstreaming] inbound data processing loop exited: transport closed (12) [Service_2021-02-19_17.32.16.txt] 19/02 20:08:33.601 {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [xrstreaming] Failed to parse PCI vid and pid from string "" {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [xrstreaming] Failed to parse PCI vid and pid from string "" {!ERROR!} [Kernel:Error] OVR Error: {!ERROR!} [DisplayManager] [DisplayManager] Failed to set power profile. [Service_2021-02-19_17.32.16.txt] 19/02 20:08:35.443 {!ERROR!} [IpcRouter] Command /bug_reporter/get_bug_info caused an error: OVR54112166 Would appreciate a Dev's thoughts on the issue and feedback!

You have got some type of confliction or hardware / software issue. Or your CPU or memory is not upto standard. I know this because I play on Syria alot, in VR no less on a 2080ti. Msaa x2 also, terrain visibility medium, trees 100%, flat shadows and low shadows for cockpit. Your doing something wrong or your pc is not healthy. I rather suspect it's down to your ram as 24gb is an odd number to have. Have you got odd units? Whata your CPU? Incidentally now I would not recommend playing DCS with high settings unless you have 32Gb of ram on a newish spec m2 SSD (samsung evo, preferred plus). Just putting a 3080 in a rig will in all fairness give you little improvements in FPS over a 2080ti as DCS is just not optimised to run the latest hardware. Thinking otherwise is just ignorant I'm afraid. You can have a 3090 but if your memory, cpu or SSD are not upto scratch a 1080 is going to perform better lol if it's in a wells setup rig. Ps note your other comments - I have no affiliation to Urga media.

This continues to be a problem for VR users - i do wish ED would take this one seriously and start looking into what's locking out the game and eating memory suddenly. Clearly its something code related the fact it suddenly bottoms out and that jumping in and out of the game can clear it more times than not. I also have experienced the same issue on the Quest 2 now, that is in addition to the Rift S and Reverb G2.

And that my friend is not the full picture. Why try and fight to the strength of your opponent, it's about the worst thing you can do. In the right player the Harrier is extremely useful, i have lost count of the amount of tomcats / viper / hornets i have virtually shot down. The biggest mistake you can force is the overshoot and many players just don't anticipate it early enough. The harriers ability to lose energy is unmatched in game or for that matter its "thrust vectoring" akak viff. You highlight it as a negative aspect however if flown correctly its actually a key attribute in winning a fight. Also it is no slouch when unloading. The key is getting to fox 2 range / the merge. The safest tactic against a harrier is to stay high at distance and fox 3, but if your over mountains and you go down to play you could very well have your pants pulled down and spanked. Also i would recommend reading Shaw's book on BFM if you can get a copy, as relevant today as it was the day it was written all those years ago. There are also guides that will take you through basic BFM.

Yes on the surface to new players it appears quite comprehensive. However with knowledge of the real life functionality and how the systems flow work then you tend to lose that appreciation quite quickly. I mean the TGP pod for a start is comical - good job there not like that in the real world otherwise the current collateral damage tally would be rookie numbers. I mean just try and talk on another aircraft or ground FAC from features on the ground by giving ground stabilised bearings from a VRP. Unfortunately also there are bugs with current implemented systems that are being marked as resolved and/or for future implementation instead of actually solving them. As for the quality in ACM, i regular shoot down tomcats, vipers and hornets PvP in a high standard server (not GS lol). If you have mountains and within visual against a skilled harrier player be careful thinking they are easy pray. Once merged even in open surroundings your equally going to struggle, those nozzles have a value!

The minimum volume is still to loud !! After 2 years please can you actually bottom this out and resolve so the players can actually control. A key binding would also be helpful......like every other developer for ED. Maybe even after the 2 year wait, introduce an analogue axis also Blood and stone springs to mind

Thanks for all the posts - i actually prefer the moving map with the black outline. The post i was originally relating to was every MFD normal screen, so the menu screen, stores page etc etc RAZBAM DO YOU INTEND TO JUST IGNORE THIS THREAD ???

Don"t be daft they do not have a good history in responding to the forums on genuine bugs. They like to use their own Discord and Facebook. Final predictions for the outcome of this issie to include; I1) It's as per SME (the same one that thinks the rose compass display is correct on the TPOD lol, instanty loses all credability ). 2) We've tested this and cannot replicate or find fault. This must be down to user hardware not being able to render correctly (as per TDC slew issue). No doubt either of these response's will mean the thread is closed and moved to resolved lol.

They should appear at the top of the MFD as two separate munitions however at the moment they do not - there lies the problem.