Gizzy
-
Posts
654 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Gizzy
-
-
....
Excellent plugin :) thanks so much for sharing.... works a treat and very easy to set up and get going.... All the bindings left out by the devs on the Harrier I can now easily access.... Great stuff :thumbup:
One I can not crack is the course bearing knob... only works in cockpit on a mouse scroll and in the plugin there is a function for it but only changes by 1 degree a button push ha ha.... anything springs to mind for 1 push to give multiple separate inputs whilst held down... just a thought...
-
https://www.digitalcombatsimulator.com/en/files/2732651/
Just tried it... works... button bindings may need some work but the keyboard bindings work fine. It's a program MOD not a saved game one.. use OvGME or similar..
As for realism, do not get caught up with hype... unless you you are flying with the same era aircraft and want a level flying field...
Use the round ones and think look under the binos for the instruments just like they still do with some A/C. I know in the Falklands war we scrounged then 'new' NVGs from the US. Likewise I've used huge non standard contraptions fitted to weaponry to accommodate starlight scopes when they first came out.... when people want the best kit to deal with adversary they will come up with something to make it work....
Hope this helps some...
-
The changelog had the deck sliding as a Known Issue, not a fix.
Thanks, my bad... I only quickly scanned the update and presumed, wrongly, it was a fix because it was bad.... ha ha now its worse.... but at least we know....
-
After update 22APR20 TARAWA deck bounce 200% worse with AV8BNA
Aircraft sometime flung 10' high, fall and disintegrate.... handbrake on, plane arm at times can be likened to dancing on ice, the crew chief really gets annoyed shouting and many times just gives up with an unable to comply.
Update notes mentioned a deck slide fix.... was it carried over to the Tarawa or the fix made deck slides worse....or is it Razbams problem... if so please move to appropriate topic folder... Thanks
-
Thank you very much Gizzy. If I may ask, why is there a separate PD measurements check box? I thought everyone had a single measurement in millimeters for the IPD (the distance between their two pupils).
Dr Google sayeth :
'A single PD is the measurement, in millimeters, from the center of one pupil to the center of the other. A dual PD is the measurement of the center of each pupil to the center of the bridge of your nose.'
:lol:
-
Great service for me, could not fault them... works a treat even with my strong prescription...
VR Optician
Dipl.-Ing. (FH) Augenoptik,
FPA Optometrist (HWK),
Arne Engler
Optik Planet
Am Sägewerk 1
85406 Zolling
Germany
Tel.: 08167/3150954
Email: info@vroptician.com
-
Get three in a row and your gear comes down just fine. Probably if you move the date on a day it will be clear...
Smile and be Happy...
-
*** MAJOR BUG - F18C ***
VR Reverb F18C
Nice one ED.... :thumbup:
ED's easter egg seen in VR. Find it yourself else the spoiler...
- Each time I drop the wheels the left MFD turns into a slot machine complete with music.... great BUT ITS BUGGED.... I keep getting three in a row but no cash comes out - Honestly ED.... a free module for each complete line should be the minimum....
Boy was my head swivelling at first, where's that music coming from... then saw the MFD WTF
then realised the date... -
Hi Gizzy, i don't know if you tried it already but your "light problem" is linked to your shadows setting "flat only", if you switch this setting to low or higher the button light is working fine, as soon as i set this to flat only i have the same problem as you have. Not sure if this should be posted in the bugs section or if this is WIP :dunno:
Well identified and thanks for coming back mate, really appreciated... I would put a kind simple note in the BUGS section just in case... :thumbup:
-
Please post some screen shots of what your seeing. My graphics are maxed out to the point of near stuttering, and I still don't see it. I don't see depth in the dials, etc. (I know they are a little shallow). It all looks very simple and toonish.
Comparing monitor views / pics between different people is not only very personally subjective but all dependent on settings, screen size monitor type etc etc...
But to help, below is a link to 4 DCS screen shots each 3440 x 1440, 2 for each aircraft - A10C & Ka50. The A/C were on the same spot (hot runway takeoff) and of course the external lighting was the same. Also remember modelled canopies are not the same, the KA50 has higher sides - armour - at the expense of viz...
2 shots are straight forward default view and the other 2 slightly zoomed in and tilted down somewhat.
And to emphasise subjectiveness, I would argue the A10 is more 'cartoonish' in 2D.
In VR wow! the A10C and the KA50 are absolutely great but the A10C has it by a whisker, in my useless opinion.
Best view the files in max native res on a 3440 x 1440 monitor...
https://www.dropbox.com/s/gcg83csuauztsup/Screen_200221_001948.zip?dl=0
-
There is always a balance between graphic resolution, polygons, FM (whats happening under the hood - old or new code) FPS and your system.
Some can handle much more - I run 4.5Mhz CPU, 32 RAM and 2080ti so sure pile it on... many others do not and have to knock down the settings to low just to get in the air...
Whatever, I certainly appreciate the upgrade, a good job especially as it was free gracias... works a treat in VR... thank you... :thumbup:
...saying that I was just as happy flying with the old cockpit, especially Ricardo's (great talent) - eye candy ain't everything - unless you're a plastic surgeon touting business....
-
Hi Gizzy,
here is what it looks on my end. Could you post a screenshot of your settings? ....
Very similar.... here's my settings but had to reduce the GAMMA considerably to make the button light effective... But at the end of a day whatever, it is better than the old for sure and love the audio!
-
Did you check the function against the light... if not, could you please do so... 'cause here is what I see....
Note the light, faint as it is... when off, auto turn works ?
........
Thats not how it is on my side, if i push the auto turn button "the light goes on" not off like on your pic.You were right UNKNOWN... despite what I was seeing.... turning the gamma down to 1.2!!! showed the lights correctly.... but ugh! to the cockpit at that setting ha haha.. thanks...
-
.......f you have direct light on that panel, then you can't recognize if it is turned on or off. Not sure if bug or feature? In RL it's hard to see some lights/LED's with direct sun light on them.
Did you check the function against the light... if not, could you please do so... 'cause here is what I see....
Note the light, faint as it is... when off, auto turn works ?
Same in all 4 maps... maybe its my bloody gremlins.... My DCS has plenty...
-
Thats not how it is on my side, if i push the auto turn button "the light goes on" not off like on your pic.
You can only check when you engage the function... auto hover, lock, move the camera with the auto turn light on, does your nose follow the camera...? now hit the button and turn the light off and try again...
If you know all this, sorry... but to me in my DCS it is back to front...
-
Or it's a problem with the english cockpit, hot start on PG on Burj Al Arab heli pad and Auto Turn turned on
EDIT: No, works also with the english cockpit.
The light is reversed for the function. Hot start and the 'auto turn' light will be on but 'auto turn' function is off.
Hit the button, the light goes off and the 'auto turn' function works... - its reversed for some reason - I'm sure it'll be an easy fix
-
Just to clarify earlier post... switch lights in the PG map are not good... no better than before.... Probably because of new lighting that was NOT installed in Caucasus Map... Some screenies...
Auto turn is OFF
Auto Turn is ON
-
For me, Good Job.... love the blade sounds..... cockpit crystal clear in VR (Reverb).... Nice...
Button lights are still not right though. In VR and 2D the Auto turn to target appears very weak but worse it appears back to front - off looks on etc...
The Autopilot cluster lights are not clear in the slightest... I can hardly discern whether they are on or off... but then that was PG map, sunny 11am.... probably ED's new lighting...
-
Gotcha... As previously said it all very subjective... everyone has to find their own settings to give, to them, an acceptable balance between FPS and graphics.
Luckily for me Reverb VR experience was not compromised going from 2.5.5 > 2.5.6 - others were not so lucky.
That's all my inputs in this post were about - showing my settings and giving some idea of an output - it might help some...
Of course the visuals in the Reverb can't compare with my Acer Predator 34" 3440x1440 GSynch which with the same settings comes in around 120FPS.... but then your neck would get a tadge sore with 2 of these strapped to your head LOL...
-
Watched the first vid and the video seemed very stuttery. Do you notice the same thing when watching that clip? It's strange, as YouTube generally smooths that out with its motion interpolation.
Other than to see the indicated FPS as shown by the DCS overhead in 2.5.6 you can NOT use that vid as an indication of smoothness.. 2 Plus 2 make Seven etc...
It was recorded by shadow NVidea in 3440 x 1440 at 60 frames per second and stepped down by an ancient free MOVIEMAKER to HD 1920x1080 but at 30 frames / second to save space on upload then fired up to YouTube who do their own magic reducing it further... to a lower spec. So forget about doing a smoothness comparison.
If you want to dig that deep into the video smoothness view the original NVIDEA file on a 3440 x x1440 monitor and you will get a better idea but again not exact.. I have copied the original file into a dropbox account for direct download... use a decent viewer such as VLC media in original format... :thumbup:
-
Let me put another point of view.
I would always recommend using SteamVR beta, as it gets updated with new options and features regularly, sometimes weeks before they hit the release version. In addition, if there is something you don’t get on with, it takes less than a minute to go back to the release version, so, no big deal.
Although it’s true that 100% gives you native res, 150% is the default, which you can see from the little vertical line on the SS slider. (As an aside, 150% is equivalent to PD of 1.2 in DCS.)
I find it rather surprising that Gizzy sees no benefit running higher SS. To me, the difference between 200% and 100% is huge. Just look at the Hornet cockpit dials. The question is however, can your system take it? SS takes a lot of resources, and, like everything DCS VR related, it’s all about compromise and getting the balance that suits you. That applies to SS, MSAA, shadows, etc. The whole thing is very much down to the individual’s preferences. ....
There are many, many factors interacting between systems - none are the same unless built the same.
Surprising or not, the stock SteamVR software settings shown (100%) give me pinsharp cockpit dials through all all models and no side stutters and so far decent FPS in 2.5.6 - MP has yet to be explored ha ha.... but of course YMMV
Me, I would always suggest standard software and only seek alternatives if I cannot achieve a result that I expect... Experiment sure, but it is easy to get into a mess if settings are not all restored to defaults when you tinker again...
Often the latest NVidea drivers often screw up my FPS and introduce side stutters..... lo and behold 1 week later a hot fix appears...
-
Colour me envious!
In case anyone else has questions...
Below is a graphic of all the settings, PC, DCS, SteamVR, NVidea etc.
In addition I made 2 rough videos capturing the VR screen without a mirror so it is rough rough but the DCS FPS counter and the topography can be seen. Unfortunately I use a SW 3440 x x1440 monitor but I resized the vid to HD but you'll get the gist okay. Hornet / Harrier / Mi8 PG map built up, very low to a few thous etc...1 day 10am June so shadows will be generated, and the other 2359. FPS was basically the same day or night and for all 3 aircraft 40 - 45 FPS down low with an occasional dip but then I was 500 knots between the skyscrapers... and 60 - 70+ at a few thousand feet.
Anyway this is just to get an idea.
It is all very subjective... what is butter smooth to me may be margarine or cooking fat to others ha ha...
Here are the 2 miz files I used. Just 3 A/C in PG... simples... https://www.dropbox.com/s/3pey0gs7bp8pvke/graphic%20test.zip?dl=0
Hope this helps.... YMMV though....
-
Hi Gizzy!
Your SteamVR settings got me confused. My Percentage values are quit different to yours, whereas I also have the same HP-Reverb here. If set to 100% I get about 25XX x 25XX resolution. To get about 2160 I have to set it down to about 72%.
The 'OLD' SteamVR settings slider I think I used to have to set 180% or thereabouts to get native Reverb res.... SteamVR auto updates my end frequently though...
On the stock SteamVR software (not beta) I get as shown below... with 2 'dots' suggesting min / max settings. As can be seen I go for the lower and this gives native Reverb res which, for me, relates to extremely good sharpness... again, for me, when trying higher settings I found no real benefit.
Hope this helps some...
-
... I'll do some more experimenting...
Might be worth having a look at NVidea driver... an update not so long ago was a dog... with stuttering everywhere .... so I rolled back to 441.20... and peace was restored.... it'll stay there for a while...
Personally, with the latest SteamVR I find hardly any advantage going above 100% giving native 2k into each eye currently giving pin sharp cockpits in all models... previous versions I was around 180% too to achieve the same clarity - but they've changed the StVR interface some....
[REPORTED][OB 2.5.6.49314] Rearming on FARP causes crash
in Game Crash
Posted
Engage any service on a FARP, it crashes.... Fly the Viggen 50% of the time it crashes. Engage a Viggen service such as kneeboard interaction it crashes... etc.
How the FARP crash was not spotted before release with the new Beta testers I can not understand unless it is hardware triggered.
dcs.log-20200520-224254.zip
test.miz