Wile E.

I created a mission with some JTACs. In the mission editor, I set the JTAC to use WP-Laser to mark the target and to prefer guided bombs. I contacted one on the radio and he gave me a nine line with "no mark" and told me to use a GBU-12. When I dropped it, there was no lasing, because the JTAC didn't turn on a laser. I didn't see a menu option to request he start lasing or smoking the target. How do I get him to do that?

That was it. Thanks. When new maps come out, will that be the only way to install them?

I'm using the latest open beta, and I installed all the map options I saw. Is there a way to verify what maps I have or change/update them?

I set up a dedicated server on a different computer. Almost everything seems to be working. I can administer it from the DCS website under my account, people can connect to it and fly missions, SRS works, etc. But when I upload a mission on the Sinai map, I can't start the mission. The run button is disabled. I paid for the Sinai map, and I enabled all maps when I configured the server. There's a log entry for uploading the mission, but no errors around it. INFO WORLDGENERAL (Main): loading mission from: "C:\DCS\Server0\Missions\simpleSinai.miz" Is there a setting I need to enable to load Sinai missions? If not, is there anything that will tell me why the server won't start a mission?

I'm trying to use the trial program. I set up 2FA almost an hour ago and my account says it's configured properly. But the store says I need to set up 2FA to trial a module. I'm assuming it's an eventually consistent system, but is it on a scale of tens of minutes or more?

TMS down fixed it. Thanks.

I'm running into this right now. If I want to create a markpoint on a SAM near steerpoint 4, and then make it the active steerpoint, is this the correct procedure: 1. Select SP 4. TGP moves to SP 4. 2. SOI the TGP and slew around to find target near SP 4. 3. Point track target. 4. Press ICP 7 for markpoints. TGP should be the active source. It should display the next markpoint. We'll say it's 26, because this is the first markpoint in the mission. 5. Press TMS up short. The target point should populate the DED coordinates. 6. Press M-SEL to make 26 the active steerpoint. 7. Press CZ to remove the cursor offset. I do that and my TGP is still pointing to the wrong location.

It's running the 2.3 release from July 6.

The Liberation generated missions I run have been crashing recently. Searching the DCS log file, I spotted this right before DCS started the minidump. Is this saying that the LotATC process caused the DCS process to crash? Or does DCS run LotATC in process? The server has LotATC active, but we didn't have any active connections at the time. 2023-07-23 01:11:17.449 INFO EDCORE (908): try to write dump information 2023-07-23 01:11:17.557 INFO EDCORE (908): # -------------- 20230723-011119 -------------- 2023-07-23 01:11:17.558 INFO EDCORE (908): DCS/2.8.6.41363 (x86_64; Windows NT 10.0.17763) 2023-07-23 01:11:17.558 INFO EDCORE (908): C:\Users\luck\Saved Games\DCS.openbeta_server\Mods\services\LotAtc\bin\lotatc.dll 2023-07-23 01:11:17.558 INFO EDCORE (908): # C0000005 ACCESS_VIOLATION at 00007ff90804b43c 00:00000000 2023-07-23 01:11:17.559 INFO EDCORE (908): SymInit: Symbol-SearchPath: 'F:\Program Files\Eagle Dynamics\DCS World OpenBeta Server\bin;', symOptions: 532, UserName: 'luck' 2023-07-23 01:11:17.559 INFO EDCORE (908): OS-Version: 10.0.17763 () 0x110-0x3 2023-07-23 01:11:17.559 INFO EDCORE (908): 0x000000000022b43c (lotatc): luaopen_lotatc + 0xF08DC 2023-07-23 01:11:17.560 INFO EDCORE (908): 0x000000000018982e (lotatc): luaopen_lotatc + 0x4ECCE 2023-07-23 01:11:17.560 INFO EDCORE (908): 0x000000000019f093 (lotatc): luaopen_lotatc + 0x64533 2023-07-23 01:11:17.560 INFO EDCORE (908): 0x00000000002a1063 (lotatc): luaopen_lotatc + 0x166503 2023-07-23 01:11:17.560 INFO EDCORE (908): 0x00000000002a14f4 (lotatc): luaopen_lotatc + 0x166994 2023-07-23 01:11:17.561 INFO EDCORE (908): 0x00000000002a1d1a (lotatc): luaopen_lotatc + 0x1671BA 2023-07-23 01:11:17.561 INFO EDCORE (908): 0x000000000027406c (lotatc): luaopen_lotatc + 0x13950C 2023-07-23 01:11:17.561 INFO EDCORE (908): 0x000000000002268a (ucrtbase): _o_exp + 0x5A 2023-07-23 01:11:17.561 INFO EDCORE (908): 0x0000000000017ac4 (KERNEL32): BaseThreadInitThunk + 0x14 2023-07-23 01:11:17.826 INFO EDCORE (908): Minidump created. 2023-07-23 01:11:17.826 INFO Lua::Config (908): stack traceback:

I didn't have the update flag. I was looking for something like that, but there's no man page or --help option that lists all the command line flags. Adding that to the command prevents it from starting the game. Thanks.

Is there a way to prevent dcs_updater.exe from starting DCS after it does its update check? I start DCS with custom commands to use openXR, and it starts with SteamVR by default, so I have to quit DCS and restart it correctly.

Piracy, most likely. But they could easily generate a signed key using your hardware that authorizes those modules on that physical device and save that for offline mode. People who update hardware at the exact time the auth server dies would be out of luck, but the vast majority of people would be able to play.

I'm having the same issue right now.

Thanks! That does exactly what I was wanting.

How can I create an explosion? That could work if I can tune the severity in the ME.