Binary

I’ve released a new update: https://github.com/rkusa/dcs-scratchpad/releases/tag/0.5.0

This has also been reported to dcs-scratchpad https://github.com/rkusa/dcs-scratchpad/issues/18. I've looked into it, and this issue is not with Scratchpad, but with all multi-line text areas in DCS. The same issue can be reproduced in all multiline text fields in DCS, eg: mission situation, red task, blue task and neutral task text fieldin the mission editor.

I don't have a white halo but am noticing something which I think has the same cause as brodie4598 described. I am seeing a blue flickering bar at the top and bottom of my view occasionally. I think the area that is rendered needs to be increased a bit. It gets worse when reprojection during low FPS situations kicks in.

Tried it with a speedboat, once I managed to established the track, it showed me its speed on the left and its mag. heading on the right of the brick, see screenshot below:

I still have the same issue, too. I have yet to find a fix for it. The odd thing is that it sometimes works for weeks just to happen again in the worst possible moment. It doesn’t seem to be an issue just related to DCS/SRS, since I found a lot of other reports of the same issue all over the internet. I personally gave up trying to find a solution and am just trying to live with it ...

Script Function: Dynamic (re)spawning and tasking of groups taking various parameters into account (like player count, groups in polygone-zones, state of other groups, ...); Communication with external APIs (to e.g. persist statistics); persist mission state between mission runs; Simulating groups/units that are not actually on the map (until certain criteria are met - example: anti-submarine warfare scenarios). Script Tool: I mostly write Lua modules (in Rust) that communicate with the mission environment via RPC calls (either via TCP or by directly polling the Lua module for RPC requests) Notes: Having a compiled program improves my change-feedback loop since I have to restart DCS / the mission less often and the compiler saves me from a lot of simple mistakes that would otherwise require a time consuming try-and-error loop. It also allows me to easily spawn other threads and move some tasks out of the scripting thread. Since this approach is probably not a common one, I still see an intersection with a lot of other tools out there: an RPC interface to the mission environment

Are you using the newest 1.0.0 alpha version and are you adding that string you’ve mentioned to a static unit (voice option only works for the static unit method and not when added to the mission briefing)?

We've observed the same (for the F18 ). Some observations: - Doesn't seem to matter a lot whether one is in IDLE, MIL or BURNER - Sometimes suddenly disappears for some seconds (without really changing the throttle significantly)

Thanks for looking into it. It might be that the initial post of the thread was a different issue. Since we ever only encountered it since the 2.5.6, and in our case there was no multi-crew in use. It also just happened again. Same effect: - No position updates from server anymore - Constant stutter Both start at the same time. The first time it happened, the stutter went away once some players had disconnected (though position updates weren't restored). The disconnecting players were all on the carrier which is why we tried the following this time. We had the one machine on the carrier take-off from it. Once it took off, the game of the player of that machine froze, but the stutter for the other players was gone. There was again nothing strange in the logs for the time the issue started and the server CPU and RAM usage during the stutter was normal. I have both the replay and the tacview, but the issue happend 1:08h after the start. So they are quite long which is why I haven't attached them for now. If they are despite their length still helpful, feel free to let me know and I'll look for a way to attach those 100 MB. EDIT: I've checked my server again and must have missed that the server (in norender) ate all my 32GB of RAM (it usually only takes around 4GB), Just in case that this might be related and helpful to know. EDIT2: Unable to reproduce by simply sitting on the carrier and letting the mission run for a while EDIT3: Just noticed from watching the Tacview files again that the position updates only stopped for aircrafts, but not for ships

We encountered the same today. It is unfortunately a carrier start replay, so probably not worth posting. But here at least the errors from DCS.log. Edit: I've removed the logs since they are related to a script in the mission and since I've checked the tacview and there was nothing in the logs that aligns to the time the position updates stopped working. Another sideeffect, besides no position updates anymore, were horrible stutters (1 sec stutters every about 5 seconds).

@streakeagle were you able to find a solution for your issue? I have the same or at least a similar issue and gave up talking to the support as well. They were re-asking the same questions over and over again - like an endless support template loop. What I've noticed is, that it is usually fine when I am only in Discord. As soon as I join SRS as well, the mic stops working after roughly an hour.

Should hopefully be fixed in https://github.com/rkusa/DATIS/releases/tag/0.9.2 Thanks for testing 0.9.0 as well, this info was very helpful for finding the issue.

Since you've already said, that you are running DATIS on 127.0.0.1, the only other thing I can think of is that the ports do not match. Is SRS running on the default 5002? Does the port you are running SRS on matches the port setting of DATIS (OPTIONS -> SPECIAL -> DCS ATIS)?

3rd party access to DCS VOIP? The interview only talked about that ED is planning to provider their own VoIP solution (at least if I didn't miss anything). The question of this thread though is more about whether 3rd party develops will be able to get access to ED's solution as well. As the author of DATIS I am really interested in this question as well, because I'd love to be able to update DATIS to also be capable of broadcasting ATIS reports to ED's upcoming VoIP solution, once it is out. This would only need documentation about the ports and packet formats send to those ports (and the approval of course to run such tools). If ATIS repots aren't enough motivation to provide access to 3rd party devs, since ED is considering to provider their own ATIS reports anyway, we could also focus on more sophisticated use-cases involving text-to-speech and speech-to-text recognition - like the mentioned AWACS bot for example.

Errors like this might be caused because of an incompatible SRS version. Use DATIS >0.10.0-beta1 for SRS 1.7 and DATIS 0.9.1 for SRS 1.6

Mission Editor Top User Requested Features I’d take WebAssembly as an alternative to Lua over all other points in this thread. If this is not going to happen, here are some other points (some suggestions have already been mentioned, though kept them in case duplicates are used to derive a priority): - Event when groups/units are RTB (example use case: know when a tanker leaves its race track or a flight its CAP station because they are empty) - polygon zones - option to enable unlimited fuel for units - random aircraft failures in MP (for non Player units) - a method to retrieve the remaining fuel of a unit - a way to change the loadout for a whole flight at once - a way to determine a unit (of a group) that used an F10 radio item (so eg adding radio items for units)

HP Reverb WMR, screen jumps occasionally? Same for me, but only when looking to the right. The issue for the headset is, that I only have a plain white wall right of my Simpit. This white wall apparently does not provide enough features for the WMR tracking to calculate its position. I’ve started hanging stuff onto that wall (patches, posters) and noticed a significant improvement. This white wall was never an issue for the tracking of the Rift S though, probably because the Rift S has way more cameras that aren’t just looking forward. So maybe trying to provide more features for the WMR tracking around you helps? https://docs.microsoft.com/en-us/windows/mixed-reality/enthusiast-guide/tracking-system

Es gibt eine neue Version (0.3.0): https://github.com/rkusa/dcs-scratchpad/releases/tag/0.3.0 Highlights: - Multi-page support - Single-player only: ein Button um automatisch alle F10 mark labels mit deren Text und Koordinaten dem Scratchpad hinzuzufügen Edit: Fixed the content migration https://github.com/rkusa/dcs-scratchpad/releases/tag/0.3.1

I've just published a new release (0.3.0): https://github.com/rkusa/dcs-scratchpad/releases/tag/0.3.0 Highlights: - Multi-page support - Single-player only: added a button to automatically insert F10 mark labels with their text and coords into the scrachpad Edit: Fixed the content migration https://github.com/rkusa/dcs-scratchpad/releases/tag/0.3.1

It was very faint for me too. It was set to an input volume of only 10% in the Oculus app. After setting it to 100%, it works fine. Though I have no idea about the other issues/questions.

It was 690,58€ for me (from HP Germany). I already had an opportunity to test one from someone else though. Resolution is superb, tacking, usability and controllers are crap though (all are probably more a general WMR issue). Still a headset I am looking forward to use with DCS.

I have a pending order at HP Germany (they opened the orders shortly aver a month ago). The last update said that current orders are postponed until mid August. Which sounds to me that they are taking the issues serious and are trying to fix them before releasing the next batches. Since I am ordering directly from HP Germany, I am not really concerned about potential issues in case of any warranty claims.

Works great since today’s patch, thanks for the fix! [emoji106]

I can confirm this, only 3DOF without sensors. I would not recommend using it without sensors in DCS. HTC Vive sensors work fine.

The ADI Yaw rate indication does not properly reflect a turn rate of 3°/sec. (Wikipedia) The F18 NATOPS state (at 2.13.4.3 Electronic Attitude Display Indicator (EADI)): In DCS, when flying a standard rate turn, the lower box is not under one of the end boxes - as seen in the attached screenshot. Additionally attached is: - a track file where I start a timer at 330° and am done with the 360° turn after 01:58min (and have the ADI page open of course) - a tacview file, which can be used to check the telemetry that show the 3° turn rate (labeled TRT in TacView) Thanks F18 ADI Standard Rate Turn 2.trk Tacview-20180701-204054-DCS-Dogfight.zip.acmi.zip