Search the Community
Showing results for tags 'need more information'.
Found 17 results
-
nullsee the screenshot. To set this screenshot up, i set my touch controllers on the top corners of my keyboard tray, with the corners passing through the palm grips of the controllers. the tray is 20 inches (50cm) wide. Note that the DCS fingers are intersecting one another by about 2 inches (5cm), meaning that the fingertip in VR is approximately 12 inches (30 cm) forward of where my physical palms are, which puts it about 9 inches (23cm) forward of where my real fingertip is. In addition, you can see that the DCS VR hand is more than one full hand-width above the grip on the controller. In VR, when i rotate my wrist 180 degrees, my VR hand traces an arc with a radius of about 5 inches (13 cm). This makes reaching some of the buttons in the cockpit extremely awkward. I understand that the Eagle devs might have higher priorities to deal with, but it has been like this since I bought my Index, more than three years ago (nearly four) now. If the DCS Dev team does not have the spare time to configure hand position data for the various touch controllers on the market, could you at least give us a set of sliders under VR options to modify the 6-axis position of the VR hands? Or if that's too much work, expose the values for this in a text file we can edit ourselves to a comfortable position? Having to work through the Kama Sutra to start up various aircraft is starting to get old.
-
During editing and testing a mission I created 4 groups of F-16s with 4 elements each. All datalinks, STN, Voice Callsigns, transmit power and flight details inserted in the editor but in-game nothing is the same. Example: Enfield 4 ship flight with STN from 00011 to 00014, Voice callsign EN11-14, transmit power high and for EN11 to be Flight Lead, during the mission is shown as EN12, STN 00011, OWN#2 which should be #1 as it's flight lead, transmit power MED and FL NO (Flight Lead). This also happens with the other elements in exactly the same way. The only option to have it in a correct way is to be manually inserted in-flight.
-
Hello, It's very confusing that I don't see a similar problem here on the forum. I'm going through the "Weasels over Syria" campaign and every time I take off, INS immediately works incorrectly. The Fix(8) - "overfly" partially helps. But I can't get it 100% correct. @Lord Vader It's really pissing me off, to be honest I've tried repair so far. Thanks ins-pb.zip
-
I have try ST, and it is no stuttering problem with it. -
need track replay F-18 Comms Menu works "off and on"
CyberJohnny posted a topic in Bugs and Problems
Hello, post the update I have been having problems with the "Comms Menu" ( Only with the F-18 module). Both in the Air, deck or ground it does not work (at least not consistently). I re-binded the keyboard, and HOTAS buttons -- no change. Frequencies were correct, even tried the "easy comms" option. Anyone else have this issue? Any Solutions? Thank you -
Game crashes, server crashes, lag spikes , stuttering, warping, time warping. what is going with DCS and the multiplayer universe. Are we going back in time, will the DCS community become extinct . With communities going back in time , yes back to the future - back to DCS . 2.6 . What is really going on with DCS 2.9 . Is DCS a conspiracy only time will tell . Watch this space for more .
-
Scenario; create a flight, 4 members, ascending STN numbers (as per default) Save the mission. Create Static Template Open new, empty mission Load static template Check STN - number 3 and 4 are switched. Seems like when generating the STN, something gets messed up. when checking the STN in a text editor, everything seems to be correct, however, upon loading it, the jets have the wrong values Test miz and STN file attached. edit; only tested with vipers, assume its the same for other aircraft too STN TEST.stm STN_TEST.miz -
EDITED per request for a clean mission with no script errors or mod dependencies. Results are essentially identical, but I did record a new video, updated the FPS numbers below to match the video, and provided a new track file. Realizing that this is a worst-case scenario where I'm looking at trees and buildings in the distance, I still feel that the performance of the TV is excessively bad compared to the FLIR, and at highest zoom level, the TADS on TV will absolutely tank any system given these testing parameters. Taking a simple single player mission, spawning at Incirlik and occupying the CPG seat. Maximum field of view with the TADS on FLIR - 85 FPS Maximum zoom with the TADS on FLIR - 78 FPS Maximum field of view with the TADS on TV - 48 FPS Maximum zoom with the TADS on TV - 14 FPS My system is a Ryzen 3800X3D with 32GB of RAM and a Radeon 6900XT with 16GB of VRAM FLIR TV FPS test (clean mission).trk Zyll Apache TADS performance - Syria.miz -
Lately I've been seeing issues with the TGP on the F16. my loadout is with guided munitions, however in the mission, the TPG never really "activates". I get the full TGP display with just a black screen. None of the MFD buttons work. before I post a bug, is anyone else seeing this, or what am I doing wrong? FYI: I'm using auto-startup procedures.
-
I've set frequencies for all the warbirds on a channel map mission in the ME. When we run the mission on our server the radios don't appear to be set. When you bring up the overlay the frequencies it shows on the 4 channels are not the ones set in the ME -
Hi Folks, i found an interesting one... but first let me say sorry in advance if my english isn´t that great, it isn´t my native language. Let´s get to the Chase, to understand my Problem here are some Details about my system in general and what runs with the Game in parallel. If anyone of ED wants to have some logs i´m gladly giving them out but not here in the post. Feel free to contact me on that matter @Eagle Dynamics. So to the Details: Ryzen 9 3900X - 32GB 3200 RAM - NVME 4.0 - RX 6700XT - 4 Displays (3 for the Game - 1 for OBS) As you may have spotted on M4 i always have opened OBS because i´m streaming DCS. OBS is encoding and rendering the stream with the CPU not the GPU. Additionally my system is running HELIOS; MUSIC for Stream; VAICOM; GREMLIN; OPENTRACK I never had this Error before, only in the last 2 days 1 time not so severe but yesterday with really heavy impact. Because i know that my RAM is not this large, i have setup the pagefile on my highspeed NVME with roughly 80GB iirc. Of this 80GB my Ram gets about 60 and the GPU gets about 20 so both have more space, this always worked fine and good till the MT patch. But please don´t get me wrong here - I LOVE THIS NEW FEATURE. Let´s get to the Point and maybe also the solution of this. What happens when I play? - I just start my game and fire all additionally mentioned software and helpers, after this I start the Multiplayer Server ingame and most of the times I then play with 2-5 friends on my locally hosted game (not dedicated) - normally we play something about 3-6 or 7 hours streight. Saturday this was also the case when i encountered the bug/showstopper the first time, we played for a few hours maybe 2 or 3 and suddenly my game starts feeling like a diashow i had about 5 or 6 frames left, so I landed and thought maybe i should restart the Game, why i thought that i don´t know... but it prevented the Chaos that ensued yesterday. After I restarted the Game everything was fine, sidenote the Game always tells me that it is CPU Bound i think this is really funny because its just at 40% with Game and Stream XD. But what i noticed, it tells me it is GPU when the stuttering apeared and also yesterday in the big chaos. The Big Chaos Yesterday: We played nearly 3 hours when suddenly my Game just starts to stutter like the last evening, I decided not to restart the Game, I wanted to know what will happen and boy was i right to do it - everything and i litterally mean everything crashed... opentrack was the first, then OBS, then Gremlin, then Helios and last but not least DCS crashed. And then i was in to investigate, the first thing i did was restarting all the Programms and try to safe my stream, which also stopped. Everything crashed again, what i didn´t know at this point DCS was still semiactive running. I then stopped everything and killed all processes in the taskmanager. Unfortunately my stream then also stopped for good for the evening. Then i went for the EVENT VIEWER to investigate and i found numerous Details on what had happend. DCS had got himself about 80 GIGS of Ram and Page file - 80!!! It was the same on the GPU i think, but there i´m not shure because there is no log for the gpu ram. So here is my theory... I think the Game just takes loads of mem when it can get it, everytime is started at an airfield it gets some GB and so on and so on, but it never get´s rid of old data in the ram, it doesn´t clean up... so it is my theory that it takes about 2 or 3 hours depending on the load i put on the system to fill up my entire ram and pagefile and then it rips up hell on my pc. After what happend yesterday i tested with the help of a buddy who has more ram then i have and we could confirm that the ST Version gets rid of old data and cleans the RAM and the MT Version doesn´t. Long story short - MT overflows the RAM and PAGEFILE and then crashes the entire PC... I hope this helps, feel free to ask any questions. Kind regards ToastyBanK3nobi DxDiag.txt dcs.log -
Hi all. With the recent update, is anyone else having issues with the viper's night vision goggles? I do not have a track file to share, but the NVG image is zoomed and not aligned. Shows a zoomed level and up to the left. I was fine before the recent update.
-
So, I edited a brand new basic edition via DCS MT 2D. When I run the mission, DCS always crash. If a take a previous mission edited via the previous version of DCS all is running perfectly. What could be the problem ? I am flying in VR (Reverb G2) via OpenXR -
Since the latest update in both ST and MT the game is now completely unplayable. Randomly the VR headset goes black for about 5-15 secs before coming back; during this the game is still rendering out the HMD to the monitor. It was working perfectly before the update. It's not the headset because the headset works perfectly in other games and in the previous version. Happens in every airframe and every map. CPU is bound in MT. 8700K oc @ 5Ghz, 64GB Ram DDR3, 1080ti, 1TB m.2 -
The game crashes when i select high on the textures, the game simples shutdown, there is no message of crash or anything else, and he crashes the discord with it, and only happens i put the textures on high, all the other configs i can seles whatever i want, liminting the fps only delays the problem.
-
When playing the F14, and press A for the RIO menu, the RIO doesn't show up and the graphic is all mess, means I can see only some part of the aircraft back, where I should see the RIO pilot figure, then all graphic artefacts. If I can I will post the screenshot.
-
George Menu is now in the middle of the screen in 4K resolution. The location is not scaled properly for higher resolutions.
