rainyday

Not really, haven't seen the bug since. But I also haven't done any naval missions recently and I've used manual fixes only.

Yeah I saw that but it was for beta patch week ago. But I suppose if you miss that, you have to wait for next beta patch? Bit unsure how this all works... Lähetetty minun T1-A21L laitteesta Tapatalkilla

Bit confused - there was a long list of Viggen updates in the latest patch, but I still have many of the bugs, like the bad engine loop sound etc. Did the patch actually go thru? Lähetetty minun T1-A21L laitteesta Tapatalkilla

I dunno if it's related to this - but some time ago something happened to breaking. I used to be able to break hard once on the ground - but currently it starts to veer of the runway really easily so that I rather not brake at all. Cant really pinpoint when the change happened though.

Thanks a lot for your awesome info anyway - it all helps me grasp how these things work. And you are probably correct - I will approach DCS Bios / Arduino on a later date on some simpler thing for a plane which is better supported. I've done basic button box stuff using Leo Bodnar boards and Xpadder - and it works great. I guess I will start there this time too.

This is an awesome campaign, having played it halfway thru so far - I just wanted to stop by and say thanks! :thumbup: It really showcases that there are many ways of doing a good campaign. I enjoyed the AJS37 Viggen introduction campaing 'Mjölnir' because of its rather short and precise missions focusing on a single aspect of a Viggen, missions mostly revolving around the single task you are doing. But this is almost complete opposite. Huge & long missions with long mission descriptions, and you're just one part of a bigger picture. But those are the things I really enjoyed in this campaign! Mission briefings really walk you thru the whole mission, you have lot on your plate but you can certainly manage that with the help of mission briefing PDF's. The campaign conveys the scale of a large operation really nicely and the longer flight times makes the missions have more 'weight' to them as you can't simply restart on a moments notice, you want to succeed. You don't feel less important though - you still want to achieve your important part of the mission (and on time!). So thanks - can't wait to see what you come up next! :thumbup:

Well that is certainly true :)

Really? I feel like for me it's more like 95%. Apart from the final manual, training missions & campaign there's not a whole lot I could ask for.

Many people do, altough Im not one of them. Whatever the case, it's the final mission of the campaign so you're not losing any of the content.

Ah - analog, makes much more sense. Looking back at the thread again - you would need to connect both ends of the resistor 'chain' to ground, and the middle to analog input if I understood correctly? Or would that be the other way around? Originally I wanted to go DCS Bios/Arduino route as it looked it has many possibilities & I wanted to try to get blinking master caution & autopilot lights (for the Viggen). But I will probably end up going Leo Bodnar route & add some Arduino, IF there's gonna be somekind of support for Viggen with the DCS Bios. I tried to research how to pull the keyboard commands from the files, but I didn't get very far how to actually implement them on Arduino. Like I said, I'm bit over my head :helpsmilie:

I can't find keybindings for the following controls: Countermeasures R - R+F - F switch Bomb interval/Wingspan selector Serie/Imp switch Grupp/Enkel switch I also can't assign 'Master Caution Reset' to anything but keyboard & mouse - other controllers are greyed out. 'Insert Data Cartridge' would be awesome to have too - as already mentioned.

Yeah, gotta love the solid feedback of a rotary switch. Resistor approach seemed inviting as an input saving method - even more so as the Viggen has quite a few rotaries.

Thanks. I think I will do that. Also, there is apparently no support for AJS37 Viggen with the DCS Bios - and it's bit over my head to get it working from scratch. So for now, I think I will go the route I know I can do - Leo Bodnar USB board and connect each of the inputs individually. :joystick:

How did it turn out? I'm just getting into DCS Bios - but couldn't find AJS37 included? Are you still working on it?

Awesome and inspirational simpit! I browsed thru your thread - but saw no mention about the size of your main screen, what size is it and do you feel like you have wide enough field of view? Im currently running 3 screen setup which I love (my main screen is 32" 16:9 which I feel is too narrow on its own - despite TrackIr) - but I'm starting my own cockpit build and I feel having 3 big screens can be bit too cumbersome. Just contemplating whether I could replace them with one bigger/wider screen without losing too much. I know I can't get as wide - but maybe there would be a sweet spot.

I feel bit ashamed - but it looks I was behind updates. I was so used to DCS World offering updates by itself during startup that I thought I was up to date. Maybe something got messed up once I moved my installation folder to an SSD, not sure. I'll get back to this if it still occurs after the update - but I doubt it. Many thanks for your help.

Looking forwards to this! Mig-23 even more - but I'm more than happy to pick this up in the mean time to get myself accustomed with the Migs :thumbup: Should be interesting plane.

I want to use Rotary Switch with Arduino. I have a rotary switch (like so: https://www.ebay.com/itm/Single-Deck-11-WAY-11-Position-ROTARY-CERAMIC-SWITCH-10mm-PCB-Panel-Mount-1P11T/302100041211?epid=2258110725&hash=item465690cdfb:g:IqgAAMXQDfdRxCz-:rk:8:pf:0) ... and Arduino Mega 2560 - and I want to make it work using 1K resistors as described in this thread: https://forum.arduino.cc/index.php?topic=340227.0 (post #13 to be specific). So far I've only made simple on-off switch connections with Leo Bodnar board - and I want to verify what I'm doing here is correct (see the attached picture). BLACK WIRE => any of the Mega Digital input ?(it's bit hard to see in the image but the black wire is in the terminal that is constantly connected no matter the switch position). RED WIRE => any of the Mega GND input ? ... Is this correct? And is that all I need to connect, have I understood correctly? Any help appreciated! (Electricity is basically magic to me so please lay it down to me like you would to a child - my desire to build DIY cockpit is far greater than my skill level... But you'll never learn unless you try, huh? :joystick: )

Just found this thread. Im still having this issue - how about others? I'm running 3 screen 5760x1080 setup. Keybindings or controllers not visible (unless hovering mouse over it) - everything just looks blank. But everything works same as before. Have not tried to assign/change any controls - but the Add Assignment Panel shows blank too. Help? Running the latest stable DCS World 2.5.

Awesome to hear, thanks! :thumbup:

Brilliant! Thanks a lot for sharing these.

Thanks, you must be right. Always learning something new about this plane... Lähetetty minun EVA-L09 laitteesta Tapatalkilla

So only the hud should point towards pop up points? I take it I won't get a distance either - other than the distance bar in the hud? Or does that just show distance to the target waypoint also? Still does not sound like the behaviour I'm getting - but I'll test some more. Thanks for your help! Lähetetty minun EVA-L09 laitteesta Tapatalkilla

I'm just struggling to get my point across as it seems... :cry: The direction is irrelevant. I've tried different numbers. I've tried 350, 330, 300, 175, 90, 45 and 30. I get that if I try to make a pop up point at the another side of the target point is silly - but I didn't read about any limitations of the pop up points anywhere so I've been testing different variations. But still, it's besides the point. What I'm saying is that when I make a target point and a pop up point - and switch between them, NOTHING changes. Distance, steering orders, hud, everything is identical whether I have chosen U or M waypoint. They are the same. They both direct me directly to the target point. Tracks are not working for me sorry - planes are always doing something else that they were actually doing.... Here's a pic of one of the missions I've tried working with. Waypoint 2 ingress, 3 is target point, trying to make pop up point roughly on the lake, inputting 175070. Am I missing something crucial here?

Ok, thanks. Will try that. Regarding the manual, you probably need to add the actual altitudes somewhere - it's impossible to know that low refers to 200m, medium 400m and so on. Especially as the low altitude bombing on page 298 in the manual refers to 'around 200m' and nothing else -- but the default is actually 400m.