sthompson

Log file shows that the mission and module are being recognized. So the problem is something else. Looks like it could be an issue with radio tuning since there is a message about no tuned units available. It would help to know your VAICOM PRO settings, which frequencies were tuned in cockpit, and whether you can contact ATC using the menu system. Also do you have easy comms on or not.

I've recently returned to the JF after having it on the shelf for quite a while. When I tried using it previously I was frustrated by problems with the antiship missiles, and I gather that those are working much better now. So recently I tried the "Sink Cargo Ship" instant action mission on the Syria map. I'm having trouble figuring out how to set a SPI for the MITL launch. There is no waypoint in the vicinity of the target ship, nor is there a PP target waypoint. So I've tried designating the target using radar (SEA1 mode). That requires a pop-up since there is a big hill creating a radar shadow from the launch point if I stay low. Popping up is getting me lots of attention from SAMs and two F-16s, but when I go down low again after launch the missile seems to lose guidance. So do I need to maintain a constant radar lock to attack in this mode? Is there some better way to provide guidance to the missile? I can't find a video of this mission online to provide some clues. The briefing mentions pre-planned RP points, but no preplanned target. Any tips will be appreciated. Also, if I change SPI after missile launch does the missile still guide to the original target point. (This is in DIR mode with target set to default setting of 40, i.e. SPI). Edit: I finally got this to work. First I learned that I need to launch in MAN mode. Then the missile will track in whatever direction it was going when it reached the last RP in the sequence. However I discovered the the mission had two RP points designated as RP4. This meant that there was no RP3 and it resulted in the missile flying towards the beach instead of the target area when it reached RP4. I fixed RP3 in the mission editor and finally was able to make things work.

I have no complaints about that. My frustrating experiences have been with cockpit snap views being included in non-editable DLC mission files, and these over-ride my own view settings. I can't think of a valid reason for a mission designer to over-ride snap views. I've complained about this to some mission designers who said they didn't realize this was happening and fixed their missions to remove the over-ride. Perhaps if these kinds of things were more transparent they could become less of a problem. My snap view settings are in the saved games folder, which is where DCS puts them when you use the prescribed method of creating those views. They are over-ridden if a snapviews.lua file is included in the*.miz file, and sometimes that does happen. As another poster noted, that's probably due to default action of the mission editor, and is not intentional.

It's especially frustrating when a mission over-rides my default cockpit snap views. I'm sure it usually happens accidentally, not intentionally.

Quoting from the Wikipedia page for indicated air speed: "IAS varies considerably from true airspeed (TAS), the relative velocity between the aircraft and the surrounding air mass." It does not mention "feel." I recommend it to anyone who, like me, might doubt that a wing "feels" anything. I also recommend the WIkipedia page for "Pitot-static system," which explains how IAS is measured and calculated (not necessarily by a computer). It's not that complicated and definitely relies on a comparison of static pressure with the pitot pressure. While it is possible that a pitot tube device also includes a static port used to detect static pressure, that isn't necessarily the case. The Wikipedia page reports that a separate static port is used in the Airbus A330 for example. But we are off topic so I won't post more about this.

As for the first statement, I'm glad we agree, although I'm not sure I know what you mean by "500 knots worth of lift." On the second point, IAS instruments compare the dynamic pressure from the pitot tube with static air pressure. If these are the same you are not moving forward. If different, you are. Dynamic pressure by itself can't give you air speed since it depends on the ambient air pressure in addition to speed.

Not quite true. If you are travelling at a ground speed of 500 knots then (ignoring wind) your wing is moving through the air at 500 knots. However the amount of lift generated depends on air density as well as speed, and the IAS adjusts for that by measuring the pressure differential in a pitot tube compared to static air pressure. A better way of thinking about IAS is that it is about the amount of air passing over your wings, not about how fast you are moving through that air. At altitude the air is thinner and so there is less air flowing for a given amount of speed.

Not nearly as irritating as all the complaining on this forum about ED's communications.

You would be wrong.

Unless you are going to do a clean install from scratch I would back up the Eagle Dynamics registry keys. These provide paths to your installations that are used by some other software (e.g. VAICOM). I've seen no indication that DCS itself uses them.

Is it possible to do a basic install without also downloading the Marianas map? Or is that also included in the 80 GB estimate?

It makes perfect business sense to give a better price to the customers who cost you less to serve.

Sense of speed is largely determined by how fast the visual appearance of objects is changing. Those changes include (a) relative size as you move closer to objects, (b) relative angle of objects off your direction of travel, and (c) changing aspect of objects as your angle relative to them changes. All of this is true regardless of your FOV. Even a realistic FOV is going to give you not much sense of speed if you focus on distant objects, especially if they are in your direction of travel because changes in view along the lines of (a), (b), and (c) occur only slowly for such objects. That's why there is a feeling of not moving when flying at high altitudes. But if you get down low and look at reasonably close objects off your 12-6 line, you should get a realistic sense of speed as you pass them, because (a), (b), and (c) are all changing relatively quickly for such objects.

So does mine. I don't think that's a problem. You might change the path entry to point to your installation on C drive and then retry KB. If it fixes it that would be helpful information to know about, so please post here.

Check to see if you have a registry entry for the openbeta install pointing to the D drive. (It would be under HKEY_User\Software\Eagle Dynamics or something similar.) If so, KB is possibly using that. Also, do you have duplicate Saved Games directories? If so that might be related. Saved Games is a system directory and you are only allowed to have one version (per user) that the system recognizes.

At least some of the issues reported were not fixed, or have returned, in the current openbeta. Last night I tried Mission 15. When tasked against the Flankers I locked all four of them in TWS mode and rippled 4 AMRAMMs, getting 3 kills. The fourth one turned back. Then I returned to WP 2 for further orders. Upon receiving orders against the inbound Fulcrums I again locked both in TWS mode, but almost instantly got a mission failed message alleging an unauthorized weapons release. But I had not fired on them. I have a screenshot to prove it, showing that I still had 4 AIM-120C on board at the time I received the message. BTW, my wingman insists on taking on the Frogfoots, and gets a SAM up the nose as a result.

I suggest the following: (1) Make sure you have the latest Community Release of VAICOM installed. (2) shut down VA and DCS, then run a repair of DCS. (3) Delete (or rename) export.lua in your Saved Games\DCS.openbeta\scripts directory. (4) Restart VA. (5) Go into VAICOM settings and make sure debugging is on. (6) Shut down VA and restart it. Then shut it down again. (7) Verify that VAICOM created a new file Saved Games\DCS.openbeta\scripts\export.lua. (8) Post your VA and VAICOM logs here.

You might want to bring this up with the community developers on Discord. However if you can't solve the problem a work around is to make sure you have the correct path set in the relevant registry keys. If you do that then you don't need to set a custom path because VAICOM PRO looks for the registry entry. This assumes you are comfortable using the registry editor. The relevant registry keys for Stable and Openbeta are as follows (edit the "data" to point to your DCS installations) ... Key Name: HKEY_CURRENT_USER\SOFTWARE\Eagle Dynamics\DCS World Name: Path Type: REG_SZ Data: C:\Program Files\Eagle Dynamics\DCS World Key Name: HKEY_CURRENT_USER\SOFTWARE\Eagle Dynamics\DCS World OpenBeta Name: Path Type: REG_SZ Data: D:\Program Files\Eagle Dynamics\DCS World OpenBeta

Neither. It's a consequence of flying high with an unrealistic FOV setting. Set your FOV to something realistic, which for most people using 2D monitors will be zoomed in pretty far. (This is realistic in terms of angular views, but will feel like tunnel vision because you can't have both good peripheral vision and realistic FOV angles at the same time with a 2D monitor.) Then fly low and fast and look at your 3-9 line. You will see the speed. Also at 12 o'clock if you are low enough.

The Wish List thread is here: It took me about 10 seconds to find it using the Forum search function. @BIGNEWY perhaps you could merge them.

Another issue is changes in trees and forests. There are a lot more now, and units that used to be out in the open may now be impossible to spot. Changes in the weather modeling can have simiilar effects. These problems can usually be solved by editing the mission, but an older mission may be unplayable without edits.

That's how I approach it too. Currently working on the MiG-19, which I purchased a long time ago, but then never tried until recently. But after reading the manual, Chuck's Guide, and going through the training exercises I'm finding a lot of unfixed bugs in the module, training missions, and included campaign. (The campaign is essentially unflyable because of comms that don't work.) Plus essentially no other SP content available either from the community or Razbam. So I'm finding it to be a bit of a disappointment. Frankly the module feels unfinished and abandoned, which makes me reluctant to buy any more from them.

That approach assumes there is enough room on the drive for an update to occur. Otherwise the update fails and there is nothing to delete. But if you have enough room for the update to finish then you don't need to do the deletion. So it's not a solution to merely delete what you don't want after every update. That said, I agree that the ultimate solution is to get a bigger drive. The symlink option is a better one than the one you propose. However, It would be nice if ED could provide some guidance and help as to code/data that doesn't need high speed access. I doubt if there is a performance need for the mission editor or the module manager or the updater to be on an SSD for example.

You can write a batch file that will prevent the next update from failing when it tries to redownload and install the unwanted files and finds there isn't enough room? That would be a good trick. Please take the 15 seconds and show us how. I'm serious.

The GFM was developed for AI aircraft and I doubt if it even could be used for player controlled aircraft. See https://www.digitalcombatsimulator.com/en/news/2021-12-03/?sphrase_id=19843819. Perhaps you meant to reference the PFM, which is used in almost all ED developed player flyable planes per https://www.digitalcombatsimulator.com/en/support/faq/general/?sphrase_id=19843819#1512209.