Rosebud47

Bought the Early Access Viper in pre sales because of the discount. I would have bought the Viper anyway. Didn´t regret it, in contrary: enjoy it very much and also enjoy that I could follow the development of it to the final release - makes the Viper somehow personal to me. Anyway, I don´t care for the exterior lights currently not implemented or some external textures, to be implemented later. I think it was the right decision of ED to give the Viper to public at this early access stage. If they wouldn´t the shitstorm in the internet would have been even greater, if the announced EA released date would have been delayed. Anyway people complain anything they could get - if it is some missing exterior light or anything, they immediately jump on to it, blow it up to a huge complaint to damnate people they even don´t know. Anyways, early access versions should get into release versions at some point and I am confident, that the Viper of ED, with the development of the Hornet in background, will be become earlier a release candidate than the modules of the significantly smaller 3rd Party developer teams.

Performancehalber verhält es sich mit VR Brillen ähnlich wie mit Monitoren. Ist halt kompletter Unsinn zu sagen: "Mein alter benq FullHD Monitor macht eine viel höhere FPS Zahl als mein neuer Samsung 4K Monitor."

After the Tomcat and Viper bought in Early Access don´t wanted to buy another one through Autumn Sale. But bought the MiG29.:-)

Don´t want to open another early access discussion here, which is dominated by a louder minority. I think, Eagle Dynamics and the 3rd Party developer already agreed to the overall community consensus, that bringing all early access modules into a final release version with ongoing bugfixing as a top priority, as for the community and in general the aircraft modules are the core of DCS World. I personally don´t need more new aircraft modules, after the EA release of the F-16. Don´t need a F-15. With the J-11A there is also coming up a 4th Gen. jet for the red, which should be considered as a very capable opponent for blue. There are always people, who demand today this airplane and tomorrow another one, without being aware of the effort in developing and the downsides for more important issues within DCS World at the moment. With regard to the announced Carrier early access in the newsletter, there is coming up a totally new element to DCS World, which might be a game changer for many organized DCS player and a most outstanding feature in the competition of flight sims. I feel there is a great changing time in DCS at the moment. Changing times always needs patience and confidence to be effective. Also I think that the current situation with early access modules of the 3rd Party developers, as well for the early access modules of Eagle Dynamics, depends on ED top priority for the implementation of Vulkan, which also touches the core of DCS World. It is understandable, the development of EA modules to not be pushed at the moment unless Vulkan is implemented, for not working hard to finish and bugfix the EA modules and then after getting the modules to the release version start again hard work for revising the work they have done before for making them properly work with Vulkan - I guess the developers would like to have this done in one working process: bringing the modules to release version and bugfixing while porting them for Vulkan. Can´t express the appreciation for looking into minor improvements, like weather/ cloud system, ingame SRS, dynamic campaign or graphical overhaul of existing older modules beside the massive changes with top priority.

Yeah, it´s fine, SteamVR shows a more appropiate resolution in normal FOV, but the 120Hz mode doesn´t work for me at the moment - doesn´t want to reduce the FOV anyway.

Great newsletter today! Surprisingly good progress on many planned things! Also love, that there´s always some attention to improved details like the missile effects. The new Ka-50 cockpit looks fantastic! Guess this DCS year will be closed with some great stuff.

You´re very welcome. The Speedmaster flight seat frame is made of steel and a very solid base. Drilling holes into it, is the hardest thing, but looking forward with some passion for the result, makes things easier. Make sure you´re using the right drill for it. For the sidemounted stick, I´ve spend a lot of time to place it in the right position, right heights by changing many times the view from the VR cockpit of the Viper to the simpit - the Mongoose T-50 CM2 is very good to simulate the FBW stick of the Viper as it is respectively slim to be placed closed to the right leg and also got a much more appropriate moving angle from the center than the WrBRD base to simulate fly-by-wire. In addition to that, the center force of the T-50 CM2 could be adjusted separately. It´s pretty expensive, but not as much as the FSSB R3 Lighting base, which is obviously the best gimble to simulate the F-16.

Hi VirusAM, yes, the table leg is exactly the one. To fix it with the Virpil base, hollow wall anchors of metal do a perfect job: Just hammer the hollow wall anchor through the plastic hole in the table leg - it will fit nice and tight. Be careful when fixing it, I´ve broke one caused by screwing to tight. Before adding the table legs, I´ve fixed the Virpil base to the Speedmaster flight seat center mount with four screws ( see picture ). Make sure that the base is perfectly aligned to your seating position straight ahead, when you drill the holes through the Speedmaster flight seat center mount plate. Finally the wooden plate on the ground got the dimensions of 69 x 46 x 2 cm to fit into the inner frame of the Speedmaster flight seat. To be sure, please measure again the inner frame. In result the center stick is rocksolid... not the slightest oscillation anymore.

Thank you! :-) I was already thinking of adding some biomutant parts painted in black to turn the VR Pit into some kind of functional H.R. Giger piece of art.

Most parts I got from the hardware store. You just need to be a bit creative and black paint color. The columns are metal table legs, 30cm - I used them upside down. With a wooden plate on the ground you could adjust the thickness needed to make it a solid and fit construction. The metal base plate of the WarBRD base is too big to fit on the center mount plate of the Speedmaster Flight Seat. You maybe have to construct some extra metal wings to stabilize the WarBRD base. In anyway there need to be drilled holes with a metal drill into the Speedmaster Flight seat.

:) love the cup holder - it´s from BlackHog.

There´s a small lever at the seat to adjust the seat position for F16C or AV8B and other jets. Yes, the center mount of the Speedmaster Flight seat is not usable without modification - I´ve used it with the metal base plate of the Mongoos T50-CM2 base, which fits as well for the WarBRD base and additional columns to fix it on a wooden plate to the ground. The same oscillating problem appeared at the right stick mounted console. It was difficult to postion the T-50-CM2 gimble in the right position for the F-16, but fits very well now. Then as well did some stabilization to wooden ground plates. On top of the right side mount, I´ve cut out a piece of the TM Warthog metal plate to cover the screws and get a plain table surface to put the small keyboard and touchpad on to it. The small keyboard I only use for GUI commands, like Comm-menu, refuel and rearm, map, Esc-button, kneeboard commands, F1 - F12 keys, etc. and as an exception from the concept the space bar as ejection seat.

VR Simpit ready for Viper A surprise was to me, that with the seat physically in the right position for the F-16, the perspective in the VR cockpit felt completely right and fantastic. Whereas with the seat in a physically up position, the perspective in the VR cockpit felt a bit off.

Don´t panic! I´m sure the question will raise again someday, somewhere in the internet.

Samsung Odyssey+ und Zubehör Verkaufe Samsung Odyssey+ 1600 x 1440 Auflösung pro Auge. Samsung Anti-SDE Beschichtung. Windows Mixed Reality. Zustand so gut wie neu. Keine Mängel. Optik, Mikrofone, Kopfhörer alles einwandfrei. Hatte die Brille nicht lange in Gebrauch und dann nur noch als Ersatzbrille im Schrank. Die Controller noch nie benutzt - Batterien für die Controller sind noch original verpackt. Von VR Cover gibt es ein dickes Gesichtspolster aus Kunstleder dazu, was sehr bequem ist. Von VR Optiker passend für die Samsung Odyssey+ Sehstärke Linseneinsätze ( -1.50 linkes und rechtes Auge ) - die Rahmen der Linseneinsätze können genutzt werden, um beim Optiker der Wahl Linsen in eigener Sehstärke einzusetzen. Die Linseneinsätze hatte ich von Anfang an und boten auch Schutz für die original Linsen der Odyssey+. Einen kaum benutzten X-Box Controller gibt es on top. 350,- € + 5,90 € Versandkosten innerhalb Deutschlands

... komplett wird das nie - gibt doch immer was, das man noch anflanschen kann :-))). Werde mit meinem VR Simpit aber auch nächste Woche dann soweit fertig, wie geplant...

Ja, das dachte ich mir auch gerade, als ich deine Bilder gesehen habe. Das passt. Die Befestigung wird bei mir etwas anders aussehen - evtl. müsste ich noch ein paar Stahl- oder Aluplatten hinter die Cougars legen, damit sie fest sitzen. Wenn ich soweit bin, mache ich auch mal ein paar Bilder :)

@rrohde Gute Idee mit den beiden Cougar MFDs! Habe meinen ursprünglichen Plan, 2 Touchpads für die MFD-Steuerung in VR zu verwenden, gerade verworfen und werde mir auch die Cougars holen. Kommst Du gut damit klar in VR? Einzig die Montage macht mir noch etwas Sorgen - die Cougar Rahmen sehen sehr leicht aus, sollten aber fest montiert sein, damit sie nicht nachgeben, wenn man mal etwas fester drückt. @maxxstv Habe den Speedmaster flight verbaut. Bin eigentlich zufrieden. Hab zwar die Hälfte der Stahlrahmen wieder abmontiert, da sie eher für Lenkradbefestigungen gedacht sind, aber die Unterkonstruktion und mit Sitz ist sehr solide und stabil. Die Halterung für den Stick musste ich nochmal mit zusätzlichen Füßen an einer zusätzlichen Bodenplatte aus Holz befestigen, damit da nichts wackelt. Bei der Warthog Base hat ein Fuß gereicht, aber bei der T-50CM2 base mussten es zwei Füße sein, damit das wirklich stabil ist. Die Firma von Speedmaster sitzt sogar in Deutschland oder Schweiz - Lieferung war schnell, wenn vorrätig.

Did not tried your settings yet, but am always very interested in your configurations and impressions. But I don´t share your opinion on the point, that increasing the render resolution by Pitool activates a hidden process for the benefit of anti aliasing. I don´t think that there´s a secret function in Pitool´s algorythms, that is more efficient due to supersampling than in SteamVr or DCS PD setting. Another point I disagree is the circumstance of downsampling by SteamVR to 20% and then upsampling by Pitool to 1.75 render quality. In my opinion downsampling should be avoided in the render process, as it effects in a loss of image information/quality. Currently I´m tryng to keep SteamVR at minimum to the native render resolution of 2560 x 1440 per eye respectively 2560 x 1616 as adjusted by SteamVR. Following the renderpipeline is still a bit mystery, but so far I think DCS´ PD setting results in a more efficient scaling/supersampling as the image is created by DCS´s graphics engine; each step after this image creation only deals with upsampling/downsampling with the predefinition and does not add more image information/quality than DCS graphics engine could do. My assumption is, that Pitool´s rendere quality setting only supersamples the predefined image. Agree that Pitools smart smoothing is efficient. So far I don´t see so much of a difference regarding the smoothness while moving the head, but I could see a difference in a tearing/ washing out effect in the cockpit without Pitools smart smoothing. Pitools smart smoothing is surely no placebo, like our individual impressions could be - I will keep it activated. In anyway we could reach comparable image quality by different approaches - interesting on this, which approach is more frametime/FPS efficient, but differences might be marginal and only perceivable in minimal difference in measured values, but not in game. Maybe there will be coming up more adjustment screws to discuss, when Pitool becomes open source. In anyway we could reach perfect image quality with the 5k+ with better performing Hard- and software behind. Especially software and compatibilty is constantly improved, whether steamVR ( openVR ) compositor or PiService compositor. Now, let´s have some fun with the witchhunters´s comments in the internet trying to destroy Pimax´innovative approach for VR at affordable prices with recent announcements. :-)))

@maxxstv Finde die Diskussion hier müßig. Es ist doch allgemein zu erwarten, dass Software nach dem Verkauf mit Updates und Patches verbessert wird - das ist jetzt wirklich nichts Neues. Es macht nur wenig Sinn, die faktische Realität, wie sie von allen wahrgenommen und erwartet wird, hier nochmal hypothetisch in Frage zu stelle. Nicht uninteressant, wenn auch offensichtlich, ist die Frage, ab wann ein Modul als EA oder als Release eingestuft wird. Ich beantworte mir die Frage damit, dass EA zwar funktionsfähig und nutzbar ist, aber noch nicht Feature complete, so wie von den Entwicklern angekündigt. Wenn für die F-16 z.B. ein TPOD als feature angekündigt ist, so ist es wohl EA, wenn man das Modul nutzen kann, der TPOD aber noch nicht implementiert ist. Ist er dann, neben allen anderen feature, implementiert, kann man dann wohl von einer Release Version sprechen, unabhängig von den bugs, die nach dem Release noch ausgebessert werden müssen. ... das ist doch alles nichts Neues? Finde EA, wie es hier betrieben wird auch recht gut: man kann das lang ersehnte Modul schon in einer früheren Entwicklungsphase nutzen, spart dafür, dass es noch nicht feature complete ist, ein paar Groschen und kann den Entwicklern feedback geben, was noch verbessert werden muss. Wenn man sagt, ´ich habe bezahlt und will dafür das fertige Modul´, tut man nur so, als hätte man etwas nicht verstanden.

Hi lefuneste01, forcing smart smoothing by file editing, like it could be done for WMR, couldn´t be done for Pimax, as the file used to edit comes with the WMR for SteamVR App and is not part of original SteamVR. Without executing Pitool, there is still running following Pimax apps in the background: - pi_overlay ( takes approx 0,3% of CPU and 12 MB of RAM ) - pi_server ( approx 3% of CPU / 50 MB RAM ) - PiService - PiServiceLauncher None of these Pimax apps could be shutdown without shutting down the headset, but they don´t take noticebale much resources. Interesting is, that SteamVR is NOT running any programm in the background as long as SteamVR is not executed. You can run DCS with the P5k+ without having any SteamVR running as GUI app on the desktop or any background running process... this confuses me, as you could adjust the render target with steamVR and then shutting down SteamVR completely - I wonder if or how the render target set by SteamVR is active, when steamVR is not running, not even in the background? Anyway, while playing around again with render resolutions, I could definitely say, that the best image quality in terms of sharpness and clarity could be only achieved by PD setting within DCS VR options. Tried different render targets with steamVR around 3000 x 1900. Pitool I don´t touch anymore and left it completely on default values ( image quality of 1.0 and only Lighthouse tracking checked ), but the image was worse than leaving SteamVR render target at 36% resulting in 2560 x 1616, but increased PD in DCS to 1.5. Give it try, would be interesting to read your impression on scaling with DCS PD only. My impression is a much more sharper image and in particular a much better image clarity by these settings. But I have to mention, that I needed to deactivate MSAA in DCS to get a good performance of approx 45 - 50 FPS / under 20 ms frametime most of the time flying. With the F5E Tiger and the warbirds the performance was even better. For a really good image clarity and view of details, DCS PD setting is definitely the best. About Pitools smart smoothing I couldn´t speak of a really noticeable difference if activated or deactivated - I got the feeling that Pitools smart smoothing does not properly interact with the openVR render pipeline and might make things more worse than better, but that´s just a feeling. Edit: I have to correct: SteamVR_Web_helper, VR compositor, VR Server and VR dashboard are the SteamVR apps which are running in the background ... it seems they are loading in the background while DCS is loading in VR ... so no confusion at least. But the background running steamVR apps don´t take so much system ressources either.

Updating the BIOS / BIOS firmware and updating mainboard/Chipset-, LAN-, USB- and OnboardAudio drivers is a good idea ... I would uninstall Process Lasso ( I think your CPU got 4 physical cores ) and reboot the system. Probably set the CPU clock/Vram back to its default values or less overclocking to exclude it as a cause in further investigation.

just to put it in the check list: have you tried to deactivate Hyperthreading in BIOS / CPU settings?

Would be interesting to know, if VRzoom works properly with the canted displays of the XTAL. In anyway this piece must be a blast. Try to fly NOE along the shorelines - it´s so much fun with a wide FOV :)))

I feel the same about this software mixture of Pitool and SteamVR... Would be interesting to see how things work out, when shutting down some running/ background running apps through the windows task manager. This week I´m very busy and off for some days from wednesday on, but surely will write here about some more testing with the newest SteamVR version. So far I would say, that the lighthouse tracking could work without using Pitool, as it is anyway Valves/SteamVR´s technology. Also I assume, that asynchrounious reprojection is also done by SteamVR only and not by Pitool. So far I understood Pitool´s smart smoothing as an addition to SteamVR´s reprojection and smoothens the 3DOF headmovement only, but not cutting the FPS into half as it is done by reprojection... hmm not sure, if there is an option to force SteamVR to do smart smoothing for the P5k+, like it could be forced by editing for WMR headsets. But there´s definitely some progress with the new SteamVR update regarding compability and support for the P5k+.