Holton181

No, can't access it, with tapatalk at least. Edit: Can be accessed in ordinary webbrowser, thanks.

So, understandable that all Belsimtek modules are put under the general 'Digital Combat Simulations' subforum now after the merge. But all threads directly under the Belsimtek subforum then? Where did they go?

When existing a flight, in the briefing window, there is a button 'save track' or something. Click it. The track is saved in '\saved games\DCS...\tracks'. So just start a flight and do your thing, then do the above.

https://forums.eagle.ru/showthread.php?p=3506042

Boy, do I feel stupid right now or what! Indeed it's in the notes, that I read before updating... Sooo, just disregard and pretend this thread doesn't exist please.

In today's update to 2.5.2.17978 the HUD got a glowing white frame around it. It's not present after mission loading before hitting the 'fly' button, but the second you do it pops right up. When going to outside view it turned out to be the landing lights, not the HUD, that turned buggy. Screenshots added.

Try a cleanup and restore first. If you don't know how to do it manually try this: https://forums.eagle.ru/showthread.php?p=2666866 Unfortunately I have no other plugin to recommend. You can export manually by some lua editing. Search the forum and you will hopefully find some instructions.

So, for whatever it's worth, in 2.5.2 OB only a few metashader for each map is created, depending on aircraft. And it's done in the new folder 'metashaders2'. No need for the tedious zooming stuff I've mentioned before. Two aircrafts that generates a metashader file for each map is the Su-25T and Ka-50. They generate the same file, so after loading a mission ones with one of them after deleting the folder and without running uMFCD, no need to run with the other one. Some aircrafts NOT generating metashader files (no need to run them before using uMFCD): TF-51D UH-1H Mi-8 Viggen These six aircrafts are the only ones I have, so you might need to try loading any additional ones yourself and see if any metashader files are created. The recreation of files in the 'fxo' folder doesn't cause crashes with uMFCD. BUT!!! In the OB branch the Deferred Shading can not be turned off!!! This means you can not really use uMFCD at the moment. Doing as I described above will stop it from crashing, but the exporting will not work correctly. Hopefully Sgt_Baker will return to this excellent project and correct what has been broken by ED

Do you mean to 2.5? No, not what I'm aware of. Still for 1.5.7, avaliable in the first post. I only corrected a small bug in mission #13, avaliable above.

Update to Mission #13 So, I've been in contact with BBQ and got his permission to post an updated version of mission #13. It is only a small thing changed. Due to possible changed behavior of some trigger conditions at some time in history one trigger did not activate, making it impossible to finish with a success rate of 100. I corrected it with no impact on the course of events. I also hide all enemy units in ME so they would not appear on the map during mission planing before mission start. Did that on some other missions too, might post them as well. I used DCS 1.5.7 (last one) for the edit. BR /H Vergeevs_group_013_eng.miz

For the Huey it's not really needed to trim, sure. But if you have the Shark it is really necessary due to how the autopilot and stability agumentation works. Mi-8 I honestly don't know if it's necessary to trim if the stick stays put.

Move the map folder to another drive and create a hardlink. Plenty of generic instructions out there.

If feasible for you, attach a stick with the length of roughly 40cm to your warthog (tape, super glue, welding or what not), reverse the axis in settings and put it on a stool on your left side as a real collective. Will do miracles. You won't be able to use any buttons though...

I have a PFT Lynx and use the "without spring and FFB" for all my helicopters (Huey, Mi-8 and the Shark). That option is indeed for our kind of controller, no spring and no FFB. But to use it you need to increase the friction on the cyclic enough so it will stay in any position when you take your hand from it. You can do that with the two nuts at the base of the cyclic, the ones opposite the potentiometers. There are two plastic washers at each location that make this possible. You really don't need much friction, I still fly with only three fingers and my wrist and the forarm on my thigh, not affected by the friction while flying. I saw a Russian blog post by one of the Belsimtek developers when this method was first introduced on how they modified an ordinary joystick by removing the spring and ading some friction to it. Cant find it now though.

Unfortunately though, to be able to map a button for Cargo View on your hotas you ned to do a small lua edit due to a small Belsimtek mistake. See post #18 here: https://forums.eagle.ru/showthread.php?p=3311348 The "Be aware 2" is no longer valid. Regarding the crew chief, it's nice to feel civilian from time to time, i.e. only you and the guy on ground without radio communication.

Or use OvGME for your modified init.lua?

Unfortunately though, to be able to map a button for Cargo View on your hotas you ned to do a small lua edit due to a small Belsimtek mistake. See post #18 here: https://forums.eagle.ru/showthread.php?p=3311348 The "Be aware 2" is no longer valid.

I've had scenarios where the download reached full competition, just to start again and again, emptying my dataplan. Turned out I did have enough space for download, but not for unpacking and install! For some reason the installer is (/was) unable to detect that little problem and never hinted anything about it, just restarted. Might have been something similar for you.

Unfortunately, when comparing changed files with those included in my mods, it was removed from the device_init.lua, didn't think of checking if the Cargo_cam.lua was still there in the Devices_specs folder though.

Thanks, this is something I never thought of!

Not necessarily. The CG should be close to it, but not necessarily in front of it. I don't know the details for the Huey though.

The main rotor is tilted slightly forward when the cyclic is dead center, to help out a little when flying forward. Due to this you need to hold the cyclic slightly behind dead center when hovering to not move forward. Hope it makes it a little bit clearer. Edit Sniped by lemoen

+1

My own feelings regarding things similar to this discussion (I'm not really emotionaly bothered by this particular one) tend to be calmed quite substantial by good communication from responsible parties, in this case Ugra-Media (not ED, nor forum mods). With more communication, at least ones a week, and hopefully recognition in bug reports and other related threads, questions answered when possible and so on (see Heatblur), even if not much new information is added. That way everyone get a feeling to be involved, listen to and valued as customers. A potential area of improvement of massive proportion with low to medium effort for Ugra-Media. Just my 2 cents.

Happy to help. Mind you, the two airdrome navpoints in the PVI-800 isn't included in the autopilot route following sequence, you have to select them manually after reaching the last WP for the AP to fly there.