RagnarDa

I think (fingers crossed) I fixed all the issues mentioned in this thread now.

Ahh sorry I was thinking of something else. Disregard #tiredddeveloper

BUG: cockpit lever (canopy closed) This has already been fixed (last night). Thanks for the report though!

Be aware that there is a differential pitch and roll gearing that makes the pitch and roll a lot more sensitive when below 350 km/h. Also, the SAS/SPAK tries to give pitch inputs so a full deflection of the stick gives 8 G's, and in slow speed this would be a very fast movement of the nose. Newer aircrafts, like the Gripen, also considers max alpha when translating pilot input to max elevon deflection and not just max G.

Although it was a while since I researched this but this is what I remember too. By "syncing" NWS and SPAK I meant maybe it should be more clever as to not fight each other.

I think it is working but the knob doesn't visually turn. Try looking at the backup compass while turning it and see if it moves. You don't need to adjust it however as it is automatically set when spawning.

Are you using a twisting stick? Guys, I've looked into this and I think the problem is three-fold: 1) The nosewheel was turning too much. I just understood, after 4 years!, that the nosewheel is supposed to be turned in radians and not in percentages! Fixed now. This will make the nosewheel about half as sensitive. 2) The SPAK corrections and nosewheel turning is not synced and maybe it should be. Figuring out how to do this best. 3) The twisting-stick issue. One thing I liked you to try is going to Controls Settings, Axis Assign and selecting the rudder input on the stick and then Axis Tune. Set the Y Saturation to something low, like 10 or lower. See if it helps and let me know the results.

Also, at what speeds do you experience the stability issue when on the ground?

I will look into this. What sort of rudder-controller do you use, twist-stick or something else?

How about now?

So... is it out yet?

Hi! Before you enter the virtual cockpit of your brand new mud-mover there are a number of things we just want to let you know we unfortunately weren't able to fix in time for the initial release. - There is currently an issue with twist stick rudder controls. Moving the rudder-control (twisting the stick) seems to be working in a relative way instead of a absolute so when you twist it one way you have to twist it the other way to cancel out your command. This issue does not affect all twist joysticks-- and we're trying very hard to find the underlying cause. This is a priority fix for us. As a temporary workaround if your stick is affected, you can use keyboard commands for the rudder. - The Bk90 cluster bomb doesn't work when in multiplayer unless you are the host. It works in single player though. We have a workaround already but it didn't make it into the release. Hopefully it won't be too long until we can implement this weapon properly. - When placing Bx-waypoints for Rb15 (Bx6-Bx9) in the Mission Editor it will sometimes not load unless you make a fix on the Bx8 waypoint (select it then T1-TV). The allowed turning is also a little more restricted (I think) than what it says in the manual: 45 degrees to Bx7 and a total of 55 degrees instead of 180 degrees. - Version 1.5.6OB of DCS has a significant cockpit shadow issue, which will make the cockpit look significantly worse than in 1.5.5. This is not Viggen specific, however. - The EP-13 Collimated sight does not collimate properly in VR. - There are Rb04 and Rb15 versions for AI planes but they where only now discovered to not work and might crash your game. The versions for human players doesn't work properly for AI. - Force Feedback doesn't work. The stick will not have centering force nor provide resistance to movement. - Probably quite a few minor or major bugs… We hope you will still enjoy our module! It has been a long road and it is surreal to finally being able to release it to the world!

I am glad this topic is brought up, since this is an issue I might catch some flak for. Mattebubben is indeed correct, the only allowed mix is gunpods and Rb75 or Rb05. This has to do not only to the J/A-selector in the cockpit but also a switch on the maintenance panel as shown in Vladinskys link. This is the way it is implemented now, ie the realistic way. I have been wanting to implement additional load-out options (selections on the "Vapenväljare") but havent had the time yet. So on release you will not be able to use a loadout like in the promo material (like Rb04+Rb75 or Bk90+Rb05) but this will be implemented post-release.

QFE Good point. I need to figure out a good way to solve this, when I eventually (hopefully) have more time. The workaround for now is: - When idling on the ramp/runway: - Check the altitude on the location of your target point. Use F10-map and hover your mouse over the point and the altitude is then shown next to the latitude/longitude. - Compare this with the altitude of the runway you are on. - Subtract the runway altitude from the target altitude. If the target altitude is above the runway altitude, you should get a positive number, and vice versa. - Set your altimeter so it displays the difference between the altitudes. For example if the runway is at 150m and the target is at 100m altitude then set you altimeter so it displays 50m. If the runway is at 40m and the target is at 80m set the altimeter so it is 40m below zero. Hope that helps!

Only the mission profile as set in the mission editor unfortunately (at the moment at least).

I've been implementing a few alternative ways to use switches but far from all of them yet. For example some of the switches that are frequently used and on the HOTAS in the real plane you are able to map in different ways ("T0-TV", and "A0-A2" for example). These work well with my Warthog setup. I didn't want to put too many alternatives in the list because it would clutter up the config screen and be confusing but I guess I could just leave them disabled but available in the lua-files.

It provides a radar-picture of the terrain in front of you so you don't fly into it

Lol!

Good catch! I though it was guided too. I will remove the guidance on the MJ2s.

I did one MJ1-only mix, one MJ2-only mix and one 50/50 of either.

DCS: AJS-37 Viggen Discussion You can designate targets with the Bk90 in the Viggen in three ways: 1. Preloaded or in-flight inputted coordinates. 2. Radar cursor while radar is in active, passive or "snapshot"-mode 3. Overflying the target and marking it You can't use the HUD unfortunately. Edit: Neither Bk90 nor Viggen itself has GPS but Bk90 has INS which guides it to the coordinates relative to the launching aircrafts own indicated position. So any error in the indicated own position in the airplane will transfer to the glidebomb.

I only have this: elements["AltsetL-PTR"] = default_axis_limited(_("Altimeter setting"),devices.FLIGHTDATAUNIT, 3306, 0, 0.001, false, false, 1)It works both for dragging and mousewheel, but it is unlimited and that's probably not what you are looking for I guess. Try enforcing the animation in code as well... :/ Updatable might mean that it accepts enforcment from the code... EDIT: You might try function multiposition_switch_limited(hint_,device_,command_,arg_,count_,delta_,inversed_,min_)with discrete steps. A large enough number of steps might not be noticeable, we humans are not very good at noticing small differences in sound volume.

I will check once I get home from work, but in general I use code to enforce the animation state just like you did in your post. It's probably not the most efficient but it works fine.

Spacehamster, I know the feeling! It is so frustrating to having to wait for something that you are looking forward to. The time before Christmas could be very stressful for many of us growing up. It is flattening that you are so interested in the modules by LNS that you take the time to write so many forum posts even on the topic of marketing strategies for products still in production. We appreciate your suggestions and it is good to have the perspective from potential consumers (even though we ourselves are also consumers of gaming-software). Also, why did you name yourself Spacehamster?

For you chart-nerds out there I generated this little thing from the FM: Please note that errors in the chart doesn't necessarily mean errors in the FM but more likely in how I calculated the numbers.