Hawkeye_UK

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.

Moki, can see your new to posting so good advice on the forums is to search back through the posts prior to posting. Rather than just logging in a posting without looking for the issue. The forums are here to also get advice and you only do that by searching also! As you can see i have already logged it literally one post down from below yours.

Unfortunately it's fair to say that the testers do not always complete a thorough job, outside the scope of this issue way to many things get missed that are pretty obvious. I'd like to see an increase in alpha testers that have more real world knowledge also with a military background rather than say a few thousand followers on youtube being a criteria. Appreciate there are some excellent testers within the community with these credentials that do an amazing job, but there are others that really i'd question whether they have the right skill set. I think the minimum criteria would be say 1500 hours with the specific ED module they are actually testing. That said when you see the developer flying around for the launch video with 10 degrees of nozzle it might to too much to hope for lol. At this point i even have serious concerns over the Razbam SME given that they are claiming the rose compass depiction on the TGP is correct. Anyone that has seen that data feed knows the reality yet here we are moved to resolved. Razbam need to be careful im picking up on quite a few things moved to resolved that have not been. Have leopards really changed their spots because this is what caused the fracture with the community last year! I should have in my original post highlighted that the EHSD txt is better however that is purely because they have put a black outline around the txt. Every other MFD screen is 50% worse if not more. Things such as engine management and take off performance being a case in point, or the cas page. I cannot see how this was a higher priority than say introducing a new weapon system at the degradation of other systems. Fly first, fight second. I perceive this is another case of the Razbam dev getting tunnel versioned about how good SVG is without actually looking at the reality. It should not have made it past his dev screen, certainly not an alpha build let alone beta.

As im sure many others are about to say - F18 will be your next module investigating the same level of commitment. Its a good time as it gets nearer to feature complete.

Title says it all really. The MFD txt is a bit of a car crash compared to how it was - the page titles are quite blurred and not sharp on the MFD's now. I'd dread to think if i had to step back to the Rift S what this looks like also, even on high resolution VR its back to leaning in again. How did this get missed - its a huge step backwards for functionality. I'm guessing its something to do with SVG (to note something which the community hasn't pressed for) and if so then this should be nipped in the bud now and thrown out as its either not working as intended or it's just poor architecture that is making the product worse.

Guys it pretty simple Il2 has been optimized for VR. Relatively speaking DCS is like a bag of spanners in the washing machine and it kind of works but its been surpassed heavily in the last few years as they have not invested in this sector early enough, or enough fullstop. Lets hope Vulcan comes sooner rather than later this year. You know there is an issue when people installing 3090's and only getting 5fps more lol. Game is heavily CPU bound - remember at the heart where still playing on an engine designed 15 years ago....

so for me it does work, surprising well wasnt expecting much from this stand alone headset but with the link - wow alot of value for £300. Title of post is very misleading to be honest. Sorry not helpful but its something hardware or software at your end. I'm guessing its something to do with not having internet - the oculus software no doubt will want to check the connection also. Try running it normally aka with internet access on your pc.

its an annoying and long running problem, its been noticeably worse in the last few months also. some type of bad memory leak somewhere. We should also have the option to turn off the hangar 3D background, its just not needed for tac command views etc. Please give us the option instead of having the GPU wearing away on a static pointless environment

@Uboats please can you review the attached track file. To note the tank in the asset pack has exactly the same issue i reported on the HQ7 and BMP some time ago - apologies its just that we have started using it and note is has severe issues. Please can you confirm logged and pass on for an urgent fix. ZtZ Test - Same problem as other chinese asset pack issues .trk

What's also a concern is that since the Harm was released on the Viper something has changed with its seeker behaviour. Nothing to do with jettisoning however when firing harms will hit sam sites that are on green in ME pretty much 100% of the time. It's an issue