Rongor
-
Posts
1583 -
Joined
-
Last visited
-
Days Won
3
Content Type
Profiles
Forums
Events
Posts posted by Rongor
-
-
You create an offset aimpoint for that steerpoint. Get into the Destination Offset Aimpoint DED pages and add the given range and bearing.
Procedure is explained in the manual page 204. -
When spawning a Hornet, regardless hot or cold start, selecting the Guard channel in any of the two radios will show an empty frequency. Players won't be able to transmit or receive on Guard.
Workaround is to load the DTC Comm partition via the MUMI page (default DTC will do, without entering and selecting a DTC in the manager)
I am not sure this should be required.Same issue for the C-preset.
-
8 hours ago, SpecterDC13 said:
Because I worked on the F16 and use to mess around with the TGP. And that is how it works. I can promise you it works as advertised.
Thanks, regarding the TMS aft, that will do.
8 hours ago, SpecterDC13 said:Because the TGP needs an image to go into regular INR in order to stabilize on.
Why though? It is supposed to maintain line of sight to coordinates, which it can do fine (within accuracy limits) during masking and switching steerpoints.
What would be the purpose of a single TMS aft to exit POINT or AREA correlation if even basic INR is also requiring an image to correlate?
So far I understood that INR is maintaining the line of sight to coordinates, even when slewed. That is exactly why it is recommended to switch from AREA or POINT to INR before the TGP is getting masked.QuoteInertial rate requires an image or it doesnt know what it needs to stabilize on. When you switch STPTs it will stabilize on a set of coords and doesnt need an image on that case.
This is contradicting the manual, which clearly states that there isn't any image processing in INR. Which only makes sense: Since the TGP doesn't need an image to stabilize on a set of coords when switching steerpoints, why would it need an image to maintain line of sight (of course this won't be pin point accurate) on the most recent coords we slewed on? This is basically the idea behind exiting the correlation track modes into INR, so I am a bit confused now about your comment claiming otherwise.
page 382:
-
8 hours ago, SpecterDC13 said:
Final conclusion: This is accurate and works as intended and here is why. You cannot CZ when the TGP is in: AREA, POINT, or INR Tracks (INR AREA/INR POINT). When in AREA or POINT notice you have to TMS AFT in order to bring it into INR first (not INR AREA or INR POINT just plain INR) in order to TMS AFT again to CZ. The reason you cannot TMS AFT 2x while in INR AREA/POINT is because that is the TGP correlating the image. You can test this out for yourself by having the TGP in front of you at the first stpt and slewing the TGP in order to have INR AREA/POINT appear and pressing TMS AFT twice to try to CZ, it will not work. So, if you have the TGP masked or it is about to be masked before you enter INR yourself, it will go into INR AREA/POINT, and that means it is attempting to correlate the image to what was stored in the memory but cannot do so. INR AREA/POINT goes away the minute you unmask.
I might be willing to believe that this is accurate only I can't see any argument presented why this should be the case.
What you describe is exactly what I described before. I am glad you experienced the same as I did.
Only how is this any hint that this is accurate?
QuoteThe reason you cannot TMS AFT 2x while in INR AREA/POINT is because that is the TGP correlating the image
I know that the TGP is attempting to correlate an image, only I don't see how this is a reason to prevent TMS AFT from functioning.
On the contrary, TMS AFT would be the logical method to stop the failing correlation by putting it into basic INR.Also the CZ next to OSB9 is evidence there is a Cursor Zero available. You can achieve it by pressing that OSB, so what is the benefit of locking out TMS aft to force the pilot to take his hand off a control to press it?
This effectively means an unnecessary degradation of HOTAS capability (admittedly a temporary and arguably unimportant one) and I can't see why avionic designers would intentional prevent TMS aft to function in this very moment.2 hours ago, BIGNEWY said:Do not expect normal tracking or cursor modes if the targeting pod is in a temporary mask.
I don't. What I expect is the TMS functions to work normal. Which in this case TMS aft doesn't for unknown reasons.
It may be accurate yet I don't see how we know it is. -
Regularly, the TGP will enter temporarily INR track mode while slewing, then the recent track mode is recommanded once slewing stops.
Occasionally, the TGP enters a continuous INR AREA or INR POINT track. This will reliably happen when the TGP is masked.
I noticed that during this state, actuating an exit out of AREA or POINT and then CZ is impossible to achieve by the usual 2x TMS aft.Pressing the CZ OSB will reliably return the TGP to the steerpoint, which often is a quick way to exit unintended masking while surveying the area. Only the TMS aft won't do in this case.
While in a continuous state of INR AREA or INR POINT, TMS LEFT, FWD and RIGHT will still work normally, so it is still possible to switch TV/WHOT/BHOT and cycle between INR POINT and INR AREA. Only TMS aft is ignored.
In the track we see me heading towards steerpoint 1 which is ahead of us. I then switch to steerpoint 2 which is behind us. The TGP following to the new steerpoint is ending up masked and INR AREA or INR POINT are displayed continuously. After applying a bit of slew, I then press all the TMS directions, all do work, only TMS aft is ignored. CZ by OSB does clear the CZ.When in regular POINT, AREA or INR, TMS aft behaves normally and applies CZ/ returns to INR and then applies CZ with 2nd press.
65 seconds track attached.
-
Intro:
I really appreciate the DTC feature coming to life and as well seeing it being introduced step by step, so that we can provide feedback while its still evaluated and improved. This thread is no criticism, I only provide my point of view, which may be totally off of what most others think but also might potentially adress what lot of other people think.
My point of view is that of a player mainly starting DCS to get into some MP server, then spawning into some dynamic slot and possibly doing so multiple times while staying on the joined server.
Situation:
Currently, when spawning into a role slot, we then enter the DTC management screen, by either opening it in the mission planner before spawning or after spawn by a keypress from within the cockpit.
Then we have to do the following steps:
1. Click on the conspirative "File" clickspot
2. click on "import"
2. navigate to a folder we will have to create before manually when saving a DTC we did populate from within the mission editor.
3. select the specific DTC there
4. done
The tedious thing about this is, that we have to do all of this every time we join a server, and whenever we have to respawn in that same slot.
All while the drop down list in the same screen for loading a DTC "available mission files" seems to be left without any use. Let's change this:
Suggestion:
Have DCS create DTC folders for each installed DTC-capable module in the savegames section. DTCs you create for this module should then save there by default. Like this:
If you then join into a server and open up the DTC management screen, the "load" drop down list should automatically be populated with all the DTCs found in the folder of the very module you are currently accessing the DTCs for.
Maybe even rename the item in the manager from "available mission files" to "available DTC".
So players would only need to select a file in this drop down list and then click load.The whole folder navigation and file selection would then be obsolete.
- Icing on the cake would be the DTC manager autoselecting the DTC file you used on your most recent flight on that module.
Advanced Suggestion:
Maybe it would be beneficial to eventually be able to save DTC files from within the DTC manager, especially the moment we get access on the nav/target points partitions and tactical stuff (just insert the specific name for whatever respective module, of course an AH-64 will have different format than a Viper) but also MFD configurations and radio/datalink presets often see a need to be adjusted while on a server mission for repeated use, so it would be great to "edit" the DTC while on ground and then save it for any future use in similar/same mission conditions.
Thank you ED!
-
2
-
-
46 minutes ago, MeanJim said:
I was flying long range SEAD missions that night, and only had the HTS, two HARMs, two fuel tanks, and some AAMRAMs. Reading back over the HAD/HTS/HARM pages in the manual, it sounds like it's not supposed to reset the cursor, but I haven't had this happen in ages.
page 407
-
1
-
-
5 hours ago, MeanJim said:
This screen shot shows the LAT/LNG on the INS DED page, which matches what I get from the F10 map. I ALT-clicked my aircraft on the F10 map to get the popup that stays when you go back to the cockpit, but I wasn't thinking and closed it when I took the screen shot.
I took this screen shot to show that the position of the waypoint should be in front of me, I don't know why the map is in MGRS, but you can convert it to see that it matches what is shown above. You can also see that the waypoint is correct on the HSD.
This screen shot is me looking over my right shoulder where it's saying the waypoint is.
Too bad your F10 map screenshot doesn't show LL, you chose to display MGRS there...
Unless TTI is running a date before 28 March 1994 (top right corner of F10 screenshot shows they do not) and/or you didn't turn the INS mode knob to NAV after alignment, there is no reason to assume you would see any noticeable drift at all, as the INS is a blended solution constantly combining INS and GPS.
Read more on this in the linked article below.Yet as your INS DED page confirms, the INS does know where you are, so the offset of steerpoints will most likely have a different reason.
@Tholozor's suggestion is pointing into the obvious direction. Always look out for CZ in your MFDs and press it when you require steerpoint accuracy again after playing around with some SOI (read more on this on page 303 in ED's manual)
Especially use of HTS can easily cause offsets in the 20 NM range.-
2
-
-
Using these lots of exclamation marks in the opening post and underlining of statements makes a possibly valid bug report seem like an unnecessary attempt to make the issue appear as the huge scandal that will shake up the entire DCS community. It won't.
-
4
-
-
This has been reported long ago
25 minutes ago, Lber657 said:so that's as far as you can go in the training mission.
You can simply ignore it and continue the mission.
-
On 5/22/2025 at 8:17 AM, Bremspropeller said:
This issue has two layers:
1) You shouldn't spawn jets at BWE if you're even semi-interested in historical/ realistic setups. The airfield is too short, not equipped and is too close to the border. Maybe OV-10s, maybe Harriers, maybe Transports (in that order of probability) and only as a fwd support base. Again, the airfield is almost within artillery range from the border. Just flying the ILS, even being vectored close and short, will probably put you into a some SAM envelopes.
2) Helicopters exist, too, and they're pretty much the only wartime use for this airfield. Hence it makes sense to be spawned where normally gliders would operate from. Also, when the Herc comes out, it should be able to operate from grass. Same with the Gina.
These are interesting layers, but don't correspond with the issue, which is the current way dynamic spawns work. Expecting players to read up which airfield historically did serve which limited types of aircraft before spawning is ignoring the fact that most servers use map modules for any kind of fantasy conflicts and the artillery you remind us of here will simply not be there.
Braunschweig's runway is about 1 NM long. Even on Tal Siman on Syria you can land an F-16 while the runway there is only half that long. Denying players the use Braunschweig for jets for historic reasons is kind of ridiculous. There are concrete spawn points at Braunschweig, so its perfectly fine for jets.The legacy spawn system doesn't have any issues with this. This thread wouldn't exist before the Dynamic slot system had been invented.
What we are seeing here is simply the new Dynamic slot system causing conflicts by randomly putting too heavy aircraft on too soft ground.
Telling people what is historic and what isn't and that you think they are supposed to use helicopters is not helpful. -
Another multicrew duo reported this happening today in the DCS discord...
https://discord.com/channels/542985647502393346/551106084157390874/1375428945914363966
also, use of grayscale confirmed
-
My report isn't meant to claim that these spots should offer a concrete floor.
The issue is that the dynamic slot system can't deal with these positions and will happily assign grass spots to unsuited aircraft.-
2
-
-
On 5/2/2025 at 8:39 AM, SloppyDog said:
I found the exactly same problem.
I tried with the bomb computer and no joy. I tried manually inputting the data (release Low Angle; pull-up time; release time) in the WSO station, and no joy.
I believe that the computer didn't accept my inputs, since I was going by trial and error. I really don't know how to manually calculate the latter two parameters.Anyway, what I'm doing with this mode is to help me engage pre-planned targets. I created this SAM site with an SA-2 and an SA-3 and assorted AAA protecting an airport. The SA-3 is easily defeated with WRGS in loft mode. The problem is the SA-2, with its long range.
The best way to defeat this situation was to use LABS mode, setup an IP and the TGT in the Mission Editor. I get very low, at around 500-1000 feet, pass the IP at 20nm from the target, do not push the pickle, otherwise as stated the missiles will be immediately fired. Jester will automatically change to the next waypoint, the TGT, and will start to call out the distance. Once at 16-15 nm, I pop up nose up 30 degrees, fire the missiles then go mid altitude to provide a target. Usually the Shrikes track the target. Closer, they will overshoot the target.
This way I've been able to use LABS mode to loft missiles, with an indication of distance and not being dependent of the WRGS system.
It is the only way LABS mode has been working for Shrikes. Not even close to what is done with bombs or to what is written in the manual.
and @tekrc
you guys might wanna scroll down the delivery mode in the bombing table...
-
I added a 128x128 px png in \Saved Games\DCS\MissionEditor\data\images\Countries\Germany\Troops and a related line into the \Saved Games\DCS\Scripts\database\troops\Germany.lua but it just won't show up.
Doesn't adding squadrons for the logbook work (anymore)?
I attached both files...
-
1 hour ago, grim_reaper68 said:
You can add this to your the list.
-Werneuchen
Zerbst, Laage had an RSBN/PRGM, Garz an KRM/GRM.
Werneuchen received its own report, due to the conflicting frequency with Havel VOR:
-
2
-
-
Spawn points 01-16 and 21-24 are affected.
Most fixed winged aircraft will be stuck in the grass upon spawn.
-
1
-
-
already reported here
-
This is a problem with selecting FCR on L6 as well.
Happens on both MPDs, pilot and CPG.
-
any idea where to receive a replacement for this internal cable?
-
18 hours ago, grim_reaper68 said:
Wiesbaden have one ILS on runway 25 (freq 108.50, ident ITOU), by the way on actual charts, WIB 88X is the correct TACAN. After a research, I found WBD but it has 28X and not 88X Tacan approach May 1966
Can you remove the ILS info? Its irrelevant that there is ILS available today. It didn't have ILS until at least 1991 (my charts AIRAC is 19SEP1991) so mentioning it here only confuses the report.
Regarding the TACAN, it had been on Ch 88 in 1991, no idea when it had been changed from 28. -
Under construction, 1968, It had been completed the next year.
-
Without many words, can the tower shaft corrected to be a cone all the way up?
-
3
-
-
11 hours ago, Cdodders said:
The trees are the real problem.
What are the trees supposed to do inside the death strip? Assist fugitives when climbing across the wall?
Also there was generally no grass. It should be all sand.
Border guards wanted to see any kind of traces from people attempting to reach the wall on foot.-
4
-
any idea where to receive a replacement for this internal cable?
HSD Mark Points
in Wish List
Posted
no workaround needed.
Offset Aimpoint is what its called.