

Talonx1
Members-
Posts
237 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Talonx1
-
Maybe same issue. No suggestions for a fix though. Its def a texture that the game is loading. Its terrible to look at depending on the random variation you get.
-
Same/similar problem that has been greatly amplified since the lighting changes in Jun 3rd update. Has nothing to do with server being paused. Dont know about SP vs MP but it happens every time I load into our running MP server and is extremely bad at night. Smudges also appear on nvg's and can sometimes cover up to 1/4 of the nvgs with bright smudges making them unusable. Changing aircraft changes the size an shapes of the smudges. I posted about it in VR bugs subsection of DCS world 2.5. Definetly a texture map of some sort as you can can some times see pinching of the mapping at polar points and in VR when its really bad you can clearly see it as a bubble surrounding your viewpoint. Its like some sort of noise map gone total haywire. Have also noticed the glare during daytime but at night the issue seems much more extreme. Seems to only be a problem during day maybe 1 out of 10 planes I load but at night it seems to be there to some extent constantly, again largly effected by the gamma setting. https://forums.eagle.ru/showthread.php?t=276474
-
In the F18 at night in VR there's all sorts of smudge around the cockpit in what looks like a bubble about 10' across (visual scale in VR). It's obviously some sort of texture map as you can see the polar coordinates pinching at times. It also seems to change when I hop into a different plane. I thought maybe it was some sort of canopy reflection issue at first but its still there, actually even brighter with the canopy open. There's also some wacky random smudging on the NVG goggles. Sometimes they are completely clear and then I can load a new plane and it's so covered in bright smudges they become completely useless. Only way to get rid of the bubble is to turn gamma completely down. Then I can't see shit else outside the cockpit either. And the only way to get rid of the smudged goggles is to load a new plane. Also theres some sort of null space box in the middle of my hud that obscures hud display. Its fairly small, only a little bigger than the size of a targeting square and any hud projection that crosses it just vanishes. Models and environment render fine behind it, just hud projection passing across it that vanishes. As if someone stuck a stamp on the hud projector lens. It sits just below and left of center. There are some obvious lighting changes that overall look pretty good but these problems are really hard to look through. Lastly the cannon at night... Maybe it's accurate I dunno but firing that thing at night now creates a massive blast. It's like I've got a fireworks display strapped to my nose.
-
Speed brakes dont auto retract in break turn
Talonx1 replied to markturner1960's topic in DCS: F/A-18C
Can also depend on how your brake is mapped. For example my brake is mapped to a dx button on my hotas which is programmed to function as a hold press. As long as the button is held its continually telling dcs "deploy brake" so even when gear drops my brake stays out. If I was deploying my brake via a single key press or holding till it was completely deployed then releasing (without sending a retract command) then the brake would auto retract when gear drops. -
Is there a mod that fixes BVR missiles?
Talonx1 replied to kraze's topic in Utility/Program Mods for DCS World
Aim 120c's can hit at like 40+ nm. All depends on aspect and target behaviour. Launching them at long range in TWS mode is pretty lethal and if they are anywhere near optimal range they are incredibly hard to avoid. Last thing they need is a range increase imo. The hud indications probably need some work though. The cue's you get seem to be way on the safe side. -
Default setting for labels are in the options menu.
-
Sounds like maybe your snap views are screwed up then. Maybe need to delete the custom views. Once upon I time I knew how, I'm sure someone else can chime in how to properly do so.
-
I also use a rift s. After taking off the hmd and putting it back on it always sticks me in the menu. Using the recent hmd shortcut has never failed to put me back into the correct position. Unless you set the key to num5 yourself then that isnt the correct keybind. I believe num5 defaults to adjusting normal view changes back to center, not VR. Make sure as well though that the dcs window is focused and that you arent in the controls menu. If you take off the hmd with the controls menu up the shortcut will not function and you'll have to scoot back to see the menu to escape it.
-
Sorry, wasnt aware of that. I havent had much time in dcs since the latest patch. Just a quick tour of the carrier.
-
In options/controls/ui layer you'll find a keybind for recenter VR. You'll be needing that a lot.
-
Its not an option its a line you add to the autoexec.exe within your savedgames/dcs/config folder. Be advised though it will also make all the new deck crew on the supercarrier only render in one eye. Along with some canopy reflections and lighting. Its really not a usefull fix.
-
bump , Any new news on this issue? It can be seriously headache inducing.
-
Have obviously brought it up but its still on devs to actually fix things. The proper solution isnt for people to turn off broken features its for devs to fix whats broken. As for razbams responsibility I dont think it should be on them at all. Its happening on ED's own F16 which flies in the face of the statement they made about it being because of how 3rd party devs design their aircraft. But if ED are just gonna sit on their thumbs and not fix it then maybe other devs can make adjustments to their modules to make them functional with the current state of the hosts software. And I hardly think increasing G loading tolerances so that planes dont fall apart in the sim qualifies as"ruining" their modules.
-
And again If it's gonna happen all the time in guns range and ED is gonna just kick the can then I think I'd rather have Razbam just unrealistically crank up the structural G limit on the mirage and harrier than continue to deal with it. As I said last time, if it was just me offline then I'd just turn it off but I don't control the servers I fly on.
-
Have only had the module for about a day but have already noticed it tends to violently depart if you try to pull hard g's. Dont know if this is the same issue but just assumed it was intentional. Also easily ripped a wing off once already Something I expect from the tomcat with wings extended but not for something as compact and rugged as a harrier.
-
Anyone know if there is a command line option that can be used to enable or disable VR? For example when I'm configuring controls I like to work outside vr so I can program voice attack and target software without taking my HMD on and off. It would be nice to be able to create a shortcut with a command line option to disable vr without having to go into vr, disable it then reload dcs again and then do it again in reverse when I'm done.
-
Oh I agree, I dont control the servers I fly on however so that decision isnt up to me. Just curious if Razbam have said anything to confirm its a known problem and if theres anything they can do on their end. Sounds to me like EF is just tossing blame because they have too many other issues to deal with. I've always thought the wake turb seemed way too strong and unpredictable. Sometimes coming in to aar its barely noticable and other times I've had it completely flip my plane over. No way that happens in real life. Theres also a mission for the f16 where you cold start on the ground and everytime I've tried it with wakes turned on the F15's taking off in front of me blow my plane over before I can even finish startup. Its broken.
-
Experienced this myself recently. Flew a mirage through an f18's wake and it tore my wings off. Anyone know if its been submitted to razbam?
-
Decksliding / Sync issues / Rubberbanding fixed for release?
Talonx1 replied to viper2097's topic in DCS: Supercarrier
False. It used to be an issue, was fixed a long time ago and resurfaced when they overlayed the supercarrier files on beta in anticipation of release. They broke a lot of things in the process. -
So carrier remains broken on mp servers... k. :noexpression:
-
Dont use viacom but VA is working fine. Dont see how DCS could effect VA functionality to begin with.
-
The drifting/sliding on deck was an issue a long time ago but has been long since fixed. Have spent the last couple of months continually running carrier ops witg zero issues. Whats happening now is a new issue.
-
100% of testing isnt end user responsibility. A good degree of "testing" should still be done in house and theres no fault in any one who expects it. You dont pay a dev to just throw some numbers into the code then release it. It "should" be tested, double tested, confirmed by internal QA and then looked at again and confirmed suitable for release by a manager. The kinds of bugs that should be making it to beta are things that can vary based in hardware configurations amd operating systems where internal testing cannot possibly be expected to cover every possible outcome. Things like the fps issues are perfectly normal and expected beta branch issues. Breaking functional code is not appropriate beta branch product.
-
Possibly cleaned up Super carrier files that werent supposed to be included in the release and were causing some servers to crash or completely fail to load. Ppl have started testing to see if it solved that problem but havent seen results yet. I assume it did.