Gliptal
-
Posts
1688 -
Joined
-
Last visited
-
Days Won
4
Content Type
Profiles
Forums
Events
Posts posted by Gliptal
-
-
I think you're missing the point. Snoopy is saying in 2D, the HUD should not be overscaned, unlike what we have now with the default head position.I am not sure what that means, obviously, it will look better in VR, and does for me, so not sure how you tested it.He talked to pilots and they said that in their resting position, they do not have to move the head to see the whole HUD. We have to do that in the sim right now in 2D.
-
Couldn't fly without this. Does it still work with the new cockpit? Can't test it for a while myself.
-
Nice!It should be possible to make it editable in future :) -
Would it be possible to add an option to set the type of a contact? In the realistic advanced profile I have to append it manually to its name while the type column remains blank. As a controller I may very well know what some flights type are (through check-ins and briefings for example).
-
No not really, I'm working on a small DCS plugin and thought of asking the experts.In general, the G force is calculated by Tacview based on your aircraft course and acceleration (averaged over one second). It is possible the G force displayed from the aircraft cockpit may have been recorded for some non FC3 aircrafts. If you see the G force in the *raw* telemetry window, then the value displayed in Tacview is the one displayed in the simulator cockpit.Did you notice any significant discrepancy with a particular aircraft?
-
Hey Vyrtuoz, may I ask you how exactly are you exporting the current G force being applied to the player's aircraft?
-
This is technically not a DS, since it's still a client hosting. The only addition is the web GUI.
Nice and handy, but not what was expected.
-
Are core clocks constant during the slowdown?
-
Setup the settings as you want them for each aircraft, and rename the client.cfg appropriately. Then use the "-cfg=" flag to load the appropriate one.
-
Check with another FPS counter (NVIDIA's or FRAPS). Either you're getting microstuttering, or something is at fault with the hardware. Have you tried switching the monitors around?
-
I'd check temps, AVX offsets, CPU UEFI settings, and core frequency changes.
-
Did he basically fly away with 3000$ worth of donations?
-
"This PC" > "Properties" > "Advanced system settings" > "Advanced" > "Settings" ("Performance") > "Advanced" > "Change".What do you mean by disabling and reenabling the custom pagefile settings? Where do I do that?Try disabling automatic management and setting the size manually. Look online for good values, there's a formula I can't recall now.
-
Actually if you read the text it does tell you to perform some action during the test.I’m pretty sure it’s automated. You press the start test and then it checks everything with out you having to do anything. I’m assuming you mean on the hud where it asks you to press enter to beginSent from my iPhone using Tapatalk
-
Don't know IRL, but that's one thing I completely disregard every time.
-
-
It still works by the way. Couldn't fly without it.
-
I have a mod for that. Is it yours by any chance?Do they plan to finally fix the cockpit switches as well? -
Latest I heard it was, but I've only seen dates for the Ka-50 lately (pushed to 2019).
-
Yeah I got past the crash either by preloading the mission running on the server I was crashing, or by resetting custom pagefile sizes on both drives. Can't seem to replicate.
-
Do you have pagefile set for both drives (OS and DCS)?
-
Do you have DCS on the same SSD as the OS?
-
Try disabling any custom pagefile settings you had, rebooting, reenabling them, and rebooting again. It seems like I can load now.
-
It seems like disabling and reenabling the custom pagefile settings I had fixed the crash. I'll see if it keeps working in the following days and reporting back.
[FIXED] HUD: A picture is worth a thousand words?
in DCS: A-10C Warthog
Posted
On the current OpenBeta (not an internal build you may have access to), with the default head position, center and pause TIR: the HUD overscans left and right.
This is what's wrong.