wowbagger

I've never understood why so many DCS players want to limit the options of others, and why they are so very vocal about it. The more people playing, the more money to develop modules and maps. Since everyone can choose to play the way they want and servers can set their own rules.... what's the point? You only harm your own prospects. Makes zero sense.

After gradually increasing the mission time hour by hour I finally figured it out. The yellow colour isn't actually lighting at all. It's a fluorescent paint that responds to the UV intensity dial. If the ambient light is bright enough it just always looks yellow. Once the ambient light diminishes, you can see the light which the fluorescent paint emits as blue. The UV switch increases the amount of blue light emitted. Works well with NVG. But in daylight conditions it will always look yellow. You can't actually 'switch' between the two colours.

Thanks for the reply Picklemonster! I feel like I've played with all those controls and still can't make it work. Perhaps I need to kill the regular lights and only use the UV knob. I'll try that and see. I didn't realize that the blue was designed for use with NV goggles. Cheers man

How to switch between them, please. I'm not really bothered as to why there are two. But I do find the yellow to be eye jarringly unappealing.

Can anyone clue me in on the yellow vs blue cockpit lighting? I only have yellow instruments. I assume the blue is for low light but - I have searched all the forums, videos and pdfs, I have clicked every button I can find, and scoured the controls settings. I can find no mention of why there are the two versions and how to switch between them. Clearly I'm missing something fairly obvious, so I have given up and resorted to a new 'help me' thread. Was this something that changed after a particular patch, or just something very well hidden in the documentation? Thanks for any guidance.

Harrier low takeoff weight encourages lots of A-A refueling.

And turn off FFB for each axis as well, unless you use it.

Note : For those who aren't bothered by F14 missing a hyphen, 'carry on, nothing to see here', go enjoy your day elsewhere, wonderfully unencumbered by such trivialities. I know I asked about this in the Bugs sub-forum, but since IronMike's reaction seemed so incongruous to the original question, and the thread was summarily closed, I think there might have been some kind of misunderstanding or miscommunication. The original question was whether the in game designation could be changed from F14 to F-14 (yes, this bothers some of us every time we see it). After messing about for a few minutes I realized that if you add a line to the entry.lua you can change it thus: The line I added was : shortName = "F-14", so that the file now looks like this: ... dirName = current_mod_path, displayName = _("F-14"), [b] shortName = "F-14",[/b] fileMenuName = _("F-14"), update_id = "HEATBLUR_F-14", ...I tested a number of missions, instant actions, skins and mods and nothing seems broken by this change. Does anyone know if this will muck up the module in any obvious way? I understand that the change would have to be reapplied after updates and repairs, as with so many mods. @IronMike, I don't want to speak for the others in the original thread, but the intent was never to concern ourselves with your folder nomenclature or how HB names things in the code. Just a simple question about this one little UI change. Apologies if that wasn't clear.

Have you inspected the usb plug to see if there is something blocking the connection, or a bend/broken bit? Unfortunately, I also contacted Buddy-Fox last autumn asking about my MIA controller. It turns out there was a Finnish mail strike. However I had to figure that out on my own since Buddy-Fox never replied to my inquiries. The controller is fantastic, the customer service not so much. There was mention earlier of the owner traveling often, but still... Anyway, your description sounds like it could be a usb connection issue. The unit is pretty easy to open up. Maybe it's possible to replace the cable without too much fuss if that proves necessary.

I have, thanks for the suggestion. They are very well done, but I kinda wish for something less practicey and more immersive - employing the C-101 for an actual mission type thing. A small COIN campaign of a few missions would bring an immense amount of fun to this underrated module.

In fact, I'd be happy just to have the ARK fixed on the -P so the module could be playable. (it is past due, gentlemen)

Currently learning the Hornet (one of my lesser favourite modules) specifically and solely for this campaign. :joystick: Can't wait.

Okay, not a bug, but can we have the Tomcat listed as F-14 instead of 'F14'? It does bug my overactive OCD. :helpsmilie: Thank you for rectifying this glaring oversight which makes the module totally unflyable. Cheers

The AvioJet is such a joy to fly. It is an excellent module which suffers from the glaring fault of having nothing to do with it. My humble advice is, please, take a break from the fettling and cook up some more missions beyond the 'navigate-from-here-to-there' type, so we can really put this beauty to use. Faffing about in the Mission Editor is the only option right now, and that state of things does a huge disservice to this fine module. Thanks for all your work on this fun little bird.

This campaign is so good. I'm only half way into it and nothing else besides Enemy Within has made DCS so engrossing and fun for me. It really showcases the potential of DCS. I made a separate 2.5.5 install specifically for this campaign, and I'm very glad I did. ED should jump all over this and come up with a deal to incorporate it into the module itself - the way Heatblur did with the AJS-37 16-2 Red Flag campaign. It will be a missed opportunity of massive proportions should this campaign fall out of the game. Anyway, Ranger79, congratulations on a fantastic piece of work, and on the new job. Thanks much for this wonderful sim experience.

Does anyone know what the OB box actually does? Is it just telling VP which Saved Games folder it should be looking for or is there something more? There seems to be a bit of voodoo involved with flicking it on or off to get this working properly in the last few months.

Looks great! It's great to have such an overview of all your campaigns, how they fit together, and what's coming up. Nicely done.

Any and all campaigns are hugely welcome, and needed. Thanks for the update!

Quite fun to fly. But not fun to use because of the aforementioned bugs -> the ARK-5 is a pain in the butt and massively frustrating at the moment. I too have parked mine for storage.

I think you'll find some parts of the world where they speak "English" to be completely unintelligible. Like Texas. Just kidding, I meant Newcastle. :P

Cheers mate.

Thanks TOViper, I think I have only flown the Viggen on the Caucasus map. Most recently I was testing to see what might be causing the the game freeze so I was doing the landing with AFK tutorial. Everything worked great until I landed and was taxiing. Using the brake axis worked to slow the plane on the runway, but after taxiing for a while, as soon as I used the brake axis again it caused the game to freeze. I tried this with and without engaging AFK, without and without engaging thrust reverser. I unmapped the Autothrottle disconnect/IR missile fast select button to remove that from the equation. It happened repeatedly regardless of these changes. The last log ended with messages like this. 2020-03-05 20:12:43.859 INFO VIGGEN: Release brake! 2020-03-05 20:12:44.431 ERROR VIGGEN: HeatBlur: Assert failed: Value out of range. -. Was nan. Expected between -2940000.000000 and 2940000.000000 @ c:\ajs37\trunk\viggennew\sources\flightmodel\aircraft_as_wing.cpp:411 I'm running 32gb ram but haven't noticed any other issues with the Viggen. I haven't read anyone else mention this issue, so I though it could be just my hardware, but thought I should wait it out until the 2.5.6. But that patch turned out to be less than ideal and I don't want to mess up my campaigns and carrier ops if I don't have to. cheers dcs.zip

Just a quick question that hopefully isn't pertinent to anyone else anymore. I have a bug in 2.5.5. Very often when I land and taxi, hitting the brakes will cause the game to freeze up and I must force quit. Did anyone have that bug before and was it fixed in 2.5.6? Was it related to the AFK bug? I haven't wanted to update until the mess that was 2.5.6 is cleaned up a bit. cheers

So you'd call him a sim-nazi? I was showing that 'scoring points' at others expense is pointless (pun intended) and not conducive to a functional community, which is what I think these forums should try to be. It was irony. Not everyone gets it, it seems. Carry on scoring your points, I guess. Good luck, I hope you win.

Very nice indeed. Thanks!