

Anubis_94
Members-
Posts
58 -
Joined
-
Last visited
Recent Profile Visitors
The recent visitors block is disabled and is not being shown to other users.
-
Maverick E (laser) doesn't track laser after fire
Anubis_94 replied to Anubis_94's topic in Bugs and Problems
As simple as it is. F18 manual here, the launch constraint circle is explained, a 15° circle (mav launch above was 24° according to tacview): I though that MAV LKD was enough, should have re-read the manual to avoid a RTFM answer Thanks . -
Hello, Sometimes, the maverick E doesn't track the laser even after : a well "MAV LKD" on the hud (anyway, the mav won't go if not locked) a target in front of the plane (~ -10° down) Laser code mav-TGP OK Here is a track on the 2.9.18.12899, as well a video and acmi. The issue is observed with the 2nd mav (2min30 mark) test_mavE.trktest_mavE.acmi
-
Hello, When exporting a .stm of a flight group with custom callsign label/number The .stm embed well the new label/number. But at import, newly created group based on .stm doesn't relfect label and number Group exported: Group after import in a new mission: Here are the .miz used to export, and the .miz after import. As well as the .stm (where BO 01/02/03/04 are well seen) Observed with F18 and F16. test_DL_Group_after.miz test_DL_Group_before.miz I would assume that all are generated at groupe creation.If yes, why include them in the .stm ? Maybe use the one in the .stm if numbers are free, then generate if number are already taken ? EDIT: I didn't see at first glance that STN is also not imported.
-
default.dtc that is loaded automatically when found by DCS
Anubis_94 replied to darkman222's topic in DTC Wish List
Adding one voice to a default.dtc, avoiding to go through the "open DTC" UI that is overkill when you just want to load an already setup one. -
Thanks @Flappie It seems that on F18 the issue is also visible on the HMD. Would you be able to add it to your comparisons ?
- 27 replies
-
- bold hud fonts and lines
- lines
-
(and 3 more)
Tagged with:
-
Release at max range OK now. Thanks
-
Exported .dtc takes way too much space on disk than needed
Anubis_94 posted a topic in DTC Wish List
Hello, I know that disk space isn't a great concern, but the .dtc is taking a lot more space than what it should. The exported json use way more space than needed, and take up to 270KB. It can be indented with a 2 or 4 space tabulation to easily use half the current space, 146KB. It can also be stripped from all these space and CRLF to take a minimal 32KB. Files attached, tested OK in game. JSON_Default.dtc JSON_Indented.dtc JSON_Stripped.dtc -
Hello, F-18 manual, page 154 : The DTC manager input is a frequence, also seen in the json export : Understanding, there is nothing to pre-configure in the DTC for this radio mode.
-
- 1
-
-
I have indeed some mod, but they are mainly cosmetics (skins), I have no return of any issue regarding other tracks I already posted here. (previous track was on an older version, maybe this is the issue, or maybe one of the other track reading problem we can see on the forum) I redid another track with a clean saved game (minus the control&graphic config). Here is the track and the video associated. Please note that, starting from max range (TMR elapsed, IN ZONE displayed, AMPCD witnessing, 1.15 in the video), I press the release button every second. I am able to release only a couple of seconds before the release cue cross the VV, as already said in my previous post. To me, I am already "well within the weapon range", and for the avionic too. Something is off, that being the manual (saying "Normally, the bomb can only be released when the aircraft is inside the LAR."), the avionic display (saying "IN ZONE"), or the weapon behavior (not allowing the release IN ZONE). I think the latter look like the most plausible, that the 24 could strike farther (as the 24 isn't a bangbang), with less energy, but that it still can go that far. Speculating that we have here a gbu12 style release but with an avionic doing a correct prediction ? G24CLARTest2.trk
-
AGM-65F Maverick missiles not working in multiplayer
Anubis_94 replied to Ladan's topic in Bugs and Problems
If you say sometimes it fires, sometimes not, it isn't the same issue as in the linked topic as we were able to always fire the SLAMER. Also, SLAMER issue is related to a desync flight trajectory from host/client. Not the ability to fire the weapon. -
As requested: tracks and ACMIs from host and client pov. Also a video from host pov (weapon release at ~2.40): Two F18, one SLAMER each, release at the same time. Each player see its own SLAMER hit the ground, and the SLAMER of the other player fly straight ahead. testSLAMERDesync_CLIENT.acmi testSLAMERDesync_CLIENT.trk testSLAMERDesync_HOST.acmi testSLAMERDesync_HOST.trk
-
Hello, I am still seeing the "missing track" flag but the track is provided in the message above. So, bumping the topic to ensure the track is seen.
-
Code need to be changed in the rearm panel now, by clicking on the little orange corner top/left of the pylon. Not via the MFD. This is only an indication for the plane, but not the bomb configuration.
-
reported Bug report: Catapult issue in multiplayer
Anubis_94 replied to Spectre561st's topic in Bugs and Problems
Hello, After encountering the issue again, here is a reproduction track with only a Roosevelt and 2 F18, ~3min Me, host, taking CATA2. Then, mate, client, taking CATA1, lag when holdback bar is set up. Wheeling. As if he wasn't allowed to move forward to catch the charriot and he was instead teleported to the chariot (?) (Bonus, he then re-extend launch bar and is sent backward) A video of the issue: https://www.youtube.com/watch?v=Pwx8a9py2m8 Please note that is for previous version 2.9.15.9599 CATA_Lag.trk -
Hello, Seen the mising trackfile tag, so here is the reproduction track. Precisely, the bomb is allowed to drop sligthly before the crossing of the VV by the release cue. Some weapon release in the red zone didn't drop the bomb, then one drop at the start of the green one. I also dropped one at the end of the green zone to confirm that the 24 was able to come back on the TGT from the min range. G24_CLAR_test.trk