TOViper

Hey D4n! Maybe you are running into the following issue, which is described in RC2 (or RC2.1beta) page 269: nullnull

so true

Hey Leadnap! According to your information, I would change page 242 in the following way (just to make the problem more clear to the reader):

Hey Machalot! OK, thanks for the clarification (also to @MYSE1234). I changed the text accordingly, and removed the [no function] tag. Page 115 now shows: Kind regards, TOViper

Thanks! Meanwhile, I corrected two errors on page 115: .) Intend of LAND / SJÖ switch was there, should not be there .) Some extra spaces where placed wrong or where missing

Hi Machalot! Since HB didn't really respond to the new RC2beta, I still do. Just a reminder, but I am sure everyone is still aware: Please keep in mind to supply information that describes the module, not the real aircraft. If you think the module should change because it is probably wrong, then try to solve the issues interneally with HB programmer first. Regarding the Doppler: on which SFI page can I find?

This one I rejected, caused by the huge amount of corrections that were made. Simply impossible, sorry guys!

Happend to me as well the day before yesterday, while I was on a MP server in Syria. Never had this before.

Hm, after reading Skyracers question again, I have to admit that I misunderstood his question. My answer was wrong (I therefore deleted my post above). Sorry Skyracer, my weak.

I requested working CBs a VERY long time ago, and I can tell you that the CB "TRIM SYST" works. If you had engaged emergency trim for any reason, the normal trim then became lost. If you pulled the CB and pushed it back in, then you had normal trim again. Can you try this, maybe something has changed again (I didn't use it for a longer time...)?

Hey Rudel, thanks for your reply on this! I am already testing my mission with this little trick and currently it works like a charm; I had no other complications or deficiencies with that.

@allguys: Thanks for sharing your experiences so far. I found what I was looking for, and I with knowing some more little details I finally decided to wait with buying something new. Furthermore, I am really looking forward for the multi-core version of DCS, which I hope gives a little boost. Also, I really hope ED manages to improve the "Terrain shadows" a bit. *fingerscrossed* Its really disappointing to see such a wonderful DCS world without shadows ... never thought it would become so important... Again, I just can tell you there is no flying DCS without VR; its still magic to me, even after years.

Handing over a "super-thanks" to you. I am looking forward in reading about your new CPU!

Hi Flappie! I need your professional opinion on this, just to confirm what I have recently talked about with Quigon. I made a screenshot of the situation: .) Pixel Density 2.0 .) Low details or even no details in the DCS settings .) No shadows at all .) Visibilty low FPS in my reference mission is about 65 fps, for which the limit clearly is the GPU. This is what the task manager says when I assign 3 cores to DCS.exe (upper row) and 3 cores to OVRServer_x64.exe (bottom row): I think a faster GPU would increase the fps significantly, and when - hopefully - reaching 90 fps (which is the Oculus Rift CV1 max fps), I can then slowly add details like shadows, clouds, etc. again. Would you agree?

Kovacs, a quick side note: You may find it useful to set "Textures" to Medium. In another thread (and this applies to my rig as well), the frame rate is better, having in mind the little less quality...

The GPU is usually the bottleneck, but of course this strongly depends on the settings I use. I chose settings before each mission ... depending on night/day, sea/land, etc. .... *pffff*

Guys, I am asking you for your experiences with the performance of latest OB 2.8.2. Maybe you find some little words describing your own experiences, please keep it as short as possible. I read that VR seems to be very performance hungry, and I also read that terrain shadows seem to cause bigger performance issues. Is there something else you have experienced? My experience - currently - is basically this: Terrain shadows OFF and on a normal single computer screen I get very good performance. Terrain shadows ON and flying in VR ... my computer really struggles. I am asking because I consider upgrading my GTX 1080 TI OC WC to another card, maybe RTX 2080. But before my final decision, I just want to clear things up a bit - at least for me, but maybe for others as well. Thanks anyway and kind regards, TOViper

Log 2023-02-06: Repaired some font errors. Repaired some typos. Repaired some PDF *gwrklwmgsngsnwqd_fckthng*. Link for download see OP. Kind regards, TOViper

OB 2.8.2.35759 SP Caucasus The mission shows the info screen for B1 at the top right corner. When the audio starts, the ATT and HÖJD buttons are hightlighted immediately, making a pilot look at them while the audio is talking about the destination indicator, which is very confusing (dicactic nonsense). The highlights should be shown a little later, when the speaker is talking about the autopilot.

If you use HD bombs, fly not higher than 150m, fly not slower than M0.8 and lower the hud. Make sure QFE is set correctly in order to see the mark on target for correct timing.

Currently I am finding no other words than ... pffff. How can the year start great without seeing what one wants to see? Hard to believe the Viggen has no fixes, but that's how it is. Next milestone: Wait for ED's multicore in order to increase frame rate ... at least.

"Is the development actually dead?" If one looks at the current changelog, one could assume that, yes. I hope they just forgot about to post the changelog...

Yep, it seems there is no way around MIST function: mist.getHeading(unit, rawHeading)

Hey Rudel! Thanks for answering, but how can I then use this parameter? Only in a trigger condition like "COCKPIT PARAM IS EQUAL TO ANOTHER"? What I in fact need is the current magnetic heading as number ... nothing more and nothing less. Sounds easy, but currently I didn't find any solution for this easy task.

OB 2.8.1.34.667.2 SP (Mission Editor) AJS-37 When I try to save the current magnetic heading ("BASE_SENSOR_MAG_HEADING") via the trigger action "X: COCKPIT PARAM SAVE AS" to a global variable called "heading_start", the value seems not to be saved. See mission file: Tester.miz