Kid18120
-
Posts
263 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Kid18120
-
-
Massive newby question here so forgive me for hijacking the thread but how do I enable the mouse cursor in game to be able to click the cockpit? I’m using the Rift S...
Thanks guys...
Settings (gear icon on the top bar in the main menu)
VR settings
Enable mouse or something like that
also make sure to enable the "confine mouse cursor to DCS window"
-
So how do you set it in the mission editor?
Just set the actual zoom (your zoom!) with the scroll wheel before saving the mission
-
I had this problem with the latest Oculus update (1.38 ) and I solved it by following this () thread, specifically replacing the 1.38 OVRLauncher.exe with older 1.37 version
Wrong thread or wrong link?
I see a guide for the "installation stuck bug" (which happened to me but solved in a totally different way) :music_whistling:
-
I've been flying the F-14 and this happens to me too, however, I think it only happens when I look at the lower right hand panel, like to adjust lights.
I look down and to the right and SNAP, I've now got my head stuck near the emergency brake.
So, I believe I've had the issue pop up other places, but it just about always happens when I'm looking at the light switches in the F-14.
-Cru
I've noticed that it happens (to me at least) when i look low-left or low-right, say UHF radio and CDU on the A10C are the angles that mess my view up for some reason.
The fact i'm not the only one makes me less worried about it :music_whistling:
Have you guys found a workaround for it? like restart everything in a certain way or something?
-
I checked the Oculus debug tool and the A syncronous warping is disabled so not sure...
I would think with a 2080Ti OC and a I7 9700 OC with medium settings I could hit 80 FPS in VR? But maybe not, waiting on updated VR maps...
Upon further investigation if I look at the sky FPS goes to 80 and looking at ground it drops to 40 FPS
Make sure the "vsync" option is disabled in DCS settings.
vsync does pretty much what asw does. If you can keep your screen's refresh rate (80Hz = 80fps) then it will "lock" there. Otherwise it will lock to the nearest lower value (the first step being half of it so 80Hz = 40fps)
-
It might be an environmental issue. Are you using the Rift in direct sunlight? Something seems to be throwing the tracking off kilter.
No, there's no direct sunlight (i also thought it might have been the issue so i started testing with the blinders closed).
Also, something i forgot to mention (editing the first post) i've tested back-to-back DCS and the other games in pretty much the exact same environmental conditions, in a matter of 30 minutes to go trough all of them. As soon as i stop DCS the issue stops and restarts as i open it. Nothing in the other games.
-
Hi everyone,
hopefully someone will be able to give me a solution to this very strange issue that i'll try to explain at my best.
First of all, i can play pretty much anything with my Rift S (Assetto Corsa, Pavlov VR, Onward, and so on) with no tracking issues of any sort.
Though when it comes to DCS, for some reason the viewpoint will not stay centered.
Once i get in the menu or in cockpit and i use the recenter view key that i've bound to my Spacebar, the view correctly resets and i find myself "sitting in the right place" so to say.
The issue is that later, sometimes after a few seconds, other times after a couple of minutes, the view "snaps down and to the left" and i find my left rudder pedal right in my face.
I can still look around in complete freedom but with this new "recentered view".
The problem is momentarily solved by recentering once again but it will happen over and over again.
At first i thought it was an issue with Rift S + mouse instead of motion controllers, so i tried disabling the "use mouse" option and leaving the motion controllers enabled, but the same thing happens and it only happens in VR mode. If i use my standard setup with track-ir everything is totally fine.
My system specs are:
- AMD Ryzenn7 2700x
- 32GB DDR G.Skill Ripjaws 3200MHz
- EVGA GTX1070 FTW (with thermal pads mod)
- DCS is the latest OB and it's installed on a dedicated SSD
Any clue? Anyone? I'm at a complete loss!
-- EDIT
Also, something i forgot to mention, i've tested back-to-back DCS and the other VR games i have, in pretty much the exact same environmental conditions, as i went through the various games in a matter of 30/40 minutes total. As soon as i stop DCS this strange issue stops and restarts as i open it. Nothing weird happens in the other games
- AMD Ryzenn7 2700x
-
Just for info, i do have a dedicated SSD (labeled as GAMES) in which i install everything that needs the extra bit of performance (DCS, ArmA3, SQUAD etc.). Everything is installed in its root (F:\whateverGame) and there's no issues with it. Just make sure any external tools (SRS and such) are pointing to the right place whenever installing/using such tools.
-
...is there a way to directly select that waypoint as steerpoint, or do I have to go through those sequentially with the switch / UFC rocker / HOTAS control?
I think, though i'm not too sure as it has been a while since i last had the need for such function, you can recall a specific STPT on the STEER page, by entering the STPT-ID / number in the top left of the MFCD (the one marked with +- symbols). Again, not totally sure as it has been a while.
-
I think i solved my crashing issues with the dreaded "Memory Access Violation" errors.
In my case it was such a simple and newbie mistake that i am guilty of have overlooked while troubleshooting my system.
It ends up that my 2 top case fans that are supposed to exhaust hot air, somewhat stopped spinning who knows when in the last 2/3 months.
Once i figured it out, i tried forcing a 100% rpm setting for running tests and DCS hasn't crashed yet, in more than 12 hours of flying in the same conditions as before.
The culprit i think is either Ryzen's memory controller or the RAM sticks themselves that were maybe undervolting because of the heat, causing the access violations.
Hopefully this was the actual cause and hopefully this post comes in handy to someone else.
-
Had a few more instances of the same damn crash in the last few flights.
Here are the log files attached. All have the same memory access violation error.
I tried reducing my preload and reducing my page file from 32 to 16 GB to no avail (last 2 logs)
-
Last i read about newer A10 variants aren't coming anytime soon due to license agreements
-
Is this in any way limited to the F/A-18C ?
In my wing they're the only once experiencing this issue (so far)
-
Having the same issue with the exact same log in the dump files (which btw are not always generated, sometimes it just kills itself with no logs).
For what i've been able to observe, to me it happens and random moments while flying the A10-C, though i doubt the A10 itself is the culprit since other friends are able to fly.
The first time it happened right after take off from Nellis AFB, as soon as i brought gears up.
Second time was while flying (still NTTR) and doing pretty much nothing, autopilot engaged in a level flight.
Third time was similar to the second, difference was a descending turn (again, NTTR).
It seems to NOT happen if i connect to the server and i'm the only one in it, though i can't be sure since it could have just been luck, the thing is all the crashes happened while there were players flying the Hornet.
I'm starting to wonder if it has something to do with it or if it is just coincidence.
I will have to test with other maps than NTTR and manage to get some time for a "solo flight" on the server.
System:
- AMD Ryzen 7 2700X (no OC other than the automatic boosting)
- 32GB DDR4 G.Skill Ripjaws 3200MHZ
- EVGA GTX1070 FTW
- 2x 500GB Crucial MX SSDs (1 for OS and 1 for DCS and other games, page file is fixed 32GB on the OS SSD)
- Windows 10 64 bit v.1903
The OS installation is relatively fresh, just wiped clean everything a couple of weeks ago, including DCS installation.
While trying to troubleshoot the issue, before realizing it was more of a "widely spread issue" here on the forums, i tried different things including repairing the DCS installation and purging the saved games DCS' directory, so i'll only be able to include last night's logs.
Another test i've made was to rollback on my graphics drivers. The first crash happened with latest 430.86. Second was with 419.67 and the third (for which logs are attached) with 430.64.
- AMD Ryzen 7 2700X (no OC other than the automatic boosting)
-
Yeah i can confirm this.
I've been experiencing this same issue on my own PC (connected as a client mind you) after the last OB update.
My sim started randomly crashing with the only error in the dump files being memory access violation 0xc0000005 at <insert here a random memory segment> .
I'll provide some logs later when i get back to my PC.
EDIT: Added logs to another thread, so here's the link to the logs package --> https://forums.eagle.ru/attachment.php?attachmentid=211903&d=1560504197
-
I've set up a mission to try the force correlate process. Targets were Shilkas and MBT's. Got some hits and some misses. I find that I'm more predictably successful with the IR Mav.
Sounds about right.
Force correlate isn't really a "free sniper rifle for MAVs". It's mainly used (if ever nowadays) for large, stationary targets. If i'm not mistaken the force correlate is simply a "picture" taken from the MAV's CCD sensor, from which then the missile aims for the dead center of said picture, which also leads to no tracking capability whatsoever - if a target moves the missile won't see it because it's aiming for that center of the picture
-
I'll make some order of what has been (correctly) reported above.
You will need to have INS aligned and in NAV mode, SAS enabled, switched from HARS to EGI and just then you'll be able to flip the EAC switch up (hidden behind and below the left throttle in the virtual pit).
Do mind that if any of the above hasn't been done, the EAC switch will return to OFF automatically.
If you have the HOTAS Warthog it will stay ON because the actual hardware switch isn't spring loaded but you will still get the EAC warning light.
S!
-
If you're talking about the user interface being too small, have you tried the "scale gui" option in the game settings?
-
I found this while going thru the task Manager and looking online to see what all those services actuall do. I think it might answer some questions. hope it helps
https://www.shouldiremoveit.com/Thrustmaster-TARGET-58707-program.aspx
So what?
I don't get the whole point of this post tbh.
You use a device for which you installed drivers that use a windows service to keep it running properly.
If you don't use the TARGET software suite you can just uninstall it and disable the service, though you might encounter issues after the dedicated USB port/hub gets disabled (sleep, hybernate, power saving plan and so on).
In modern computers (anything able to run DCS actually) the resources used by such service are negligible anyway
-
Would be nice if they also limited the A10 to combat loads.
Why would you do that?
True, the A10 does have combat loads but is also able to carry more, as such the aircraft in DCS is able to carry more stuff and it's up to the user to choose the appropriate loadout.
Also combat loads are usually standardized within squadrons and not necessarily are the same for everyone
S!
-
Awesome, thanks :D
-
Hi Ciribob,
seems like this latest release of SRS doesn't work with F/A18 anymore, still works with A10C though
-
-
We eat Falcons for breakfast! :smilewink:
When you don't crash upon landing (joking, i love the 39 :thumbup: )
S!
ECM pod
in DCS: F-16C Viper
Posted
Though i have no official sources for this, just my own understanding on the matter which is only based on a few reads over the course of the years and some combat-simming experience.
I believe the externally mounted pod instead of the internal module is for a matter of convenience.
It's certainly easier to maintain / replace when you compare it to an internal module, plus it allows for "choices" on which type of pod to carry, based perhaps on base's availability, unit's cost, threat level, tasks and so on. It also allows for flexibility in case you don't actually need it, since you can just remove the pod and save yourself the extra weight, whereas the internal module is always there even if you don't need it.
It's true that you do end up losing the center line pylon for an ecm pod, but is also true that said center line is rarely used in actual combat scenarios, as you'd tend to prefer the double tank on the wings for the extra fuel, especially in CAP-kind of tasks, where you need a lot of time on station and still be able to drop the extra fuel (and consequent weight) and gain the needed agility and performance for an actual engagement. Anyone correct me if i'm wrong of course.