TOViper

Guys at HB, I wish the best to you for getting all the fixes work properly and make every effort you put it worth it! HB rocks.

Done. I had to remove all WAV files from the missions, thus they might now work. Anyway, you can analyze them in terms of the warehouses. The problem is the programming strategy they used for the EQP tab. Instead of adding new DCS items to the end of the list and show the list sorted alphabetically, they somehow changed indexes of existing items (which is a killer). At least this seems to me when looking at this.

Hello Nealius! From a technical point of view it makes sense to turn the nose into the wind in order to avoid starting problems and overheat of the cowling. Aircraft usually allow for a maximum tailwind component for engine start (e.g. not more than ~5-10 knots). To be honest I am not sure if this is the logic of the game because the programmers took this into consideration, or simply a bug.

Just to make clear what I was talking about: In the "A/C" tab: The strategy to show newly added aircraft to DCS with a value of 100 is a good idea. It is not a problem to change the number, e.g. to zero. This step is - in fact - not really necessary, because during creation of the mission in the past the new aircraft were not available. Fine! In the "EQP" tab: The problem arises in the equipment tab. Once the mission is opened in a newer DCS version, the first lines - depending on which content was added - are emtpy, and with a number of 0. If I want to add the newly created weapons of my new DCS version to this specific mission, I have to first click "Unlimited Munitions", save the mission, and then uncheck this check box. This - of course - kills all settings from the past, and I have to reconfigure all numbers from scratch. These are my two cents on that. I am still not sure if the other guys are talking about the same or have other problems. Flappie: I could send mission via PM, is that OK?

I have to add that it is not required to fly a full loop in order to get the freeze. Today I flew 70° nose up, then rolled half, and went down. After reaching normal flight attitude the sim stopped (was a reverse half cuban eight).

De nada my friend. What would we do without a manual? Loosing our minds sometimes ...

According to manual RC2 - and according to my understanding - the steering orders (bearing & distance) should be as follows: ADI: U point and M point HUD: U point and M point CI: M point only(!) I made a track where you can see my inputs right before take-off: - TAKT - IN - 22506 - B2 (which is M2 because it has a time-on-target TOT defined via the mission editor) - OUT - AKT POS After lift-off and reaching 400km/h, the waypoint B1 is selected automatically, showing the steering orders on CI, ADI, HUD. When passing B1, the next waypoint U2 is selected automatically, showing the steering orders on ADI, HUD. After passing U2, the M2 target point is selected automatically, showing the steering orders on CI, ADI, HUD. Viggen_PupUp-Point_working_on_HUD_and_ADI_as_intended.trk

Seems not working anymore in OB 2.7.8.16140. Do you guys have luck?

Hello Sturmvogel! According to other user posts (including my own experience), this is not unusual. Friend of mine and me had to re-assign some bindings, and do a full check for all controls (especially all buttons/switches on the HOTAS/stick/throttle/rudder).

Yep, wrong alert. After 1 hour of flying a few sorties I got the freeze again. 2021-11-26 21:04:19.949 ERROR VIGGEN: HeatBlur: Assert failed: Value out of range. -. Was nan. Expected between 0.000000 and 6.283185 @ e:\dcs\viggen git\ajs_5\trunk\viggennew\sources\flightmodel\flightdataunit.cpp:695 DAMN

Seems gone with update OB 2.7.8.16140. Can someone confirm?

To be honest, I guess so, but I indeed remember seeing this effect once too, but wasn't able to reproduce it with the current OB 2.7.8.16140. I will fly the Viggen a bit this weekend, maybe I will catch it again, or - hopefully - don't catch it anymore.

Hey Machalot! I am not able to reproduce this, can you create a video?

Hi! I recently noticed, that the throttle lever (the one in the cockpit) jumps a bit rearward when increasing my own throttle lever. This happens only in the 100% MIL power range. See my short video: At 00:04 I start increasing throttle on my Warthog, and at a certain stage right before reaching 100% MIL the lever in the cockpit jumps rearwards (00:13). The other way around: decreasing the lever from AB zone 1 to MAX MIL the same: decreasing the real throttle lever makes the cockpit lever jump forward when reaching the 100% MIL setting. It is not related to the calibration setting of my Warthog, I also tried it out using keyboard only with disconnected Warthog. I assume this is just a bad animation of the throttle lever going up and down the detent ... does it? What I am also missing is the click when going from MAX MIL to zone 1 and backwards ...

Imagine you would have written "B-52 forum". User xxxx: "Oh, there is a B-52 in DCS? Cool . Where can I download it?". Bug-Tracker at ED: "User xxxx says he can't find the B-52 module for buying it." TOTAL CHAOS (loved_by_Joker)

LOL, yep, that might happen. Seeing not even one bug fixed makes me think: ok, I'll focus on the new functions of the F-16. Since a few months this bird speeds up massively, faster than I am currently able to keep track (AND training). In the near future, once I got enough of this modern digital freaking shitty display symbols datalink superboring stuff not seeing one enemy close, I come back to the oldish Viggen, and again find the love of my life. I kindly ask you to have the beast ready then

Read a few postings above, just want to add 2 cents: At least I would right now love to have: .) a "NEXT LAUNCH" command I can send to Jester .) a "RESET RADAR TWS" command to start from scratch (center horizontally and vertically in TWS manual) .) a "RESET RADAR RWS" command to start from scratch (center horizontally and vertically in RWS) Both in Jester Menu and ViacomPro. The rest I am currently able to handle (more or less) using calls like e.g. "scan sector angels 20 for 30" (I use VIACOMPRO) using information from AWACS or GCI.

Boosterdog, where can I find this thread please?

Can confirm this. Used Kutaisi as L1 (9014), then entered a new reference point somewhere on the map by using new coordinates for L1. Then I entered a new landing runway heading via BANA/GRÄNS. When then switching to REF/LOLA > UT it still shows 901400, alternating with the LOLA coordinates the aircraft is currently located.

Windows settings: Windows Gaming Mode disabled? Graphics Performance Setting for DCS.exe set to "High performance"? Captures disabled? Nvidia Control Panel: Power Management Mode set to "Prefer maximum performance"? Texture filtering - Quality set to "High performance"? DCS settings: Visibility set to "Medium"? (all above are VERY expensive ... ) Shadows set to "Flat"? Ground shadows set to "Flat"?

Thanks for posting a very old wish of mine! Meetoo +1

which problem? a) with the instructions or b) you have still long loading times and stutter when passing other players?

Hey RuskyV! I worked a lot with links in the past, so it was very funny for me to see the long description about one single command in the shell Anyway, even beginners will have a good description, and kudos for your efforts from my side. But I still have a question to you relating to Windows interals (you might be a professional,... are you?). You wrote: "By moving files outside the program executable but maintaining the path tricks windows into thinking that these files are no longer being commonly accessed thus freeing up memory purely for DCS without interference from windows." Just for my understanding: Is it that Windows now "sees" that the folder (in fact the link) is empty (but pointing to another directory), and thus doesn't start loading any (textures, ...) files from this folder into its own Windows cache/memory? Allow me to shorten you description for the non-beginnners: .) Change to the directory containing the DCS installation, e.g. c:\games .) Remember original DCS directory name, e.g. DCS.Openbeta .) Rename original DCS directory e.g. to DCS.Openbeta.backup .) Create new DCS directory with any name, e.g DCS.Openbeta.new .) Start Command-Shell (CMD.EXE) - There change to the directory that contains the DCS directories, e.g. type the following: cd C:\games - There type the following: mklink /j "C:\games\DCS.Openbeta" "C:\games\DCS.Openbeta.new" .) Cut all directories and files from the DCS.Openbeta.backup folder and paste them in the newly created DCS.Openbeta.new folder .) Play DCS and have fun Let's see if the low-fps-when-passing-multiplayer-buddies problem is gone ... Anyway, thanks bud for this fantastic tip! Kind regards, TOViper

As the title says, the Sidewinder tone stays on after firing the last missile on an aircraft with smokepods mounted. Mission out of editor, SP, 2.7.7.15038 OB Since the tone is generated by the missile, there shouldn't be no further tone if the last missile was fired. Smokepods on stations 1A + 8A Sidewinder 9M on stations 1B + 8B Here are the mission and the track-file: F-14A_Sidewinder_Tone_stays_on.mizF-14A_Sidewinder_Tone_stays_on.trk

Thanks buddy, this solution works solid as a rock! You are my man for today!