Silver_
-
Posts
230 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by Silver_
-
-
Thanks for your reply, my friend. That's what I'm doing so far, but I hope they fix it.
-
2
-
-
I've noticed that keybindings (Left Ctrl+1, +2, +3 ,...) aren't currently working when I try to activate ASW on my Quest 3 within DCS. I'm not sure why this is happening now.
Thanks.
-
1
-
-
Personally, with my Quest 3 and QVFR I get a much higher quality than VD's Godlike mode, of course I'm using DLSS and wired link and I only use the Oculus Tray tool to change the sound from my glasses to the computer and vice versa. That said, with my 3090, I can't use mode J and K because I notice a drop in performance. On the other hand, I use mode E which gives me higher image contrast and very good performance (72 frames in most situations), with some ghosting (very little) but I've gotten used to it. I have the fovetted region adjusted so that my eye doesn't see the box with the naked eye, I have to look very far to the edge of the lens to see it.
-
On 4/27/2025 at 10:42 PM, CapnCoke said:
Disable the mod. Delete. Download and Enable the mod. Maybe something wasn't loading right.
And to clarify surveillance flights and friendlies detected by surveillance are blue while members and other f18s are green. I wish I can get members to blue but from the way its coded it's not possible. Maybe I'll find a way.For some reason, the modernmpd.lua file didn't copy. Fixed, thank you very much. @CapnCoke.
-
Hi @CapnCoke , on the SA page, I see all the symbols in white except for the enemies, which are red. Before, I saw my flight members in blue and those of other friendly flights in green, but now they all appear white. What am I doing wrong? , I hope you can clarify this for me. Thanks.
-
Sorry, friend, I didn't see your post because it wasn't in the right bugs section. This post refers to a previous one I sent, but I had problems recording a track and resubmitted it.
-
1
-
-
Well, I have no idea, my friend, that happens to me when I record a track using VR, but in 2D I have no problems, at the moment.
-
Hi @NineLine, sorry for reopening this post. I finally managed to record the track without errors. The problem was that when recording the track in VR mode, it just gave me an error.
To give you a quick rundown of what I did, I loaded a personal DTC for the F-18, where all the radio frequencies are in AM (mainly so I could talk with the Vipers). None are in FM.
However, when flying the plane, after loading the cartridge, it is observed that some frequencies, such as preset 1 and preset 8, are, curiously, in FM. In the track I sent you, you can see how I try to change this to AM, but the button simply does nothing; the change to AM does not occur. The only way to change to AM is to press this button and then press the rotary frequency button, and magically it changes to AM. If I press the button again to switch to FM, the change does not occur either! It only happens once I press the rotary frequency button, regardless of whether I press the radio 1 or radio 2 button.
In the track I finally managed to record, without errors or corruption, the problem is clearly visible.
Greetings and thank you very much for your interest.
-
2
-
-
Try in 2D instead of VR my friend. It goes, it's a problem I had and I couldn't send a track to DCS. In VR it just doesn't work.
-
2
-
-
I can't make a short track for you with instant action. I always get this error:
-
Do you need the data cartridges too o or only the track?Sorry, the track you submitted is corrupt. Can you send a new one? In the meantime, I will try and reproduce based on your description.
Enviado desde mi SM-A336B mediante Tapatalk
-
When I load the cartridge into my F18, the Comms partition, doesn't respect the channel type, whether it's AM or FM, and it plays whatever it wants. I have all the F18 channels programmed in the cartridge as AM so I can talk to the F16s, but because of this bug, it switches presets 1 and 8 to FM on the plane, without having programmed them that way, just it does whatever it wants.
When I try to manually change in flight, for example, channel 8 to AM (it's on FM, DCS mysteries) IT DOESN'T LET ME!!!
-
Just now, CapnCoke said:
My bad. Meant 2.1.52
No problem my friend, clarified.
-
30 minutes ago, CapnCoke said:
Is that with v2.5.2 or v2.5.1? I'm on v2.5.2 and doesn't seem to happen to me.
Are you referring to 2.1.52 or 2.5.2? If it's the latter, I don't know where to download it.
-
I have seen that when I apply your mod, on the EWR screen, when selecting AUTO or S/A (semiAUTO) a long number appears next.
-
Steps to follow:
Enter into some instant F18 action in the Caucasus, specifically BVR 8 vs 8
Press the new DTC button before hitting Fly.
Modify some parameters within the new cartridge, specifically these:
-Add the AUTO 1 program one more flare.
-Switch when detecting LAUNCH of Mig29 to AUTO1
Close the cartridge and then press Fly.
Inside the aircraft configure all your avionics:
-Load cartridge (ONLY press ALR67, you don't need to modify comunications this time)
-Activate and set your EWR to AUTO mode.
When the Mig29 launches a missile at you, your automatic program may be activated, but you may get a nice crash.
Report information to DCS. This is very important.
-
I only experience stuttering and therefore frame drops when I enter missions with a lot of troops attacking on the front lines. If it's a mission with a low load, I don't even realize it exists. This happens to me especially at the beginning of a campaign.
I'll have to try the antivirus exclusions thing you mentioned, but I'm not entirely sure it will fix it.
-
1
-
-
I've done a lot of testing with this, and I personally prefer preset E because on my 3090, in J and K modes, it eats up frames and also makes the image look less contrasted. Perhaps those latter modes would work better on more advanced graphics cards, but not for me.I tried preset J and K (DLAA), both looks very crisp in general, except ghosting pretty bad in F4 TV screen (with either AGM45 or Pave spike). Did a clean install of the latest Nvidia driver and ghosting in TV screen was gone but turns out it reset the preset to default ©... did a few more test and ended up with E to keep a non-smeared TV screen.
Anyone else having similar issue?
Enviado desde mi SM-A336B mediante Tapatalk
-
10 hours ago, Tholozor said:
The laser code is technically not part of the fuze, it's part of the guidance control section. The FMU-152 tail fuze only allows the pilot to electronically change the arming and function delay timing, nothing more.
Thanks for the clarification, my friend. I wasn't aware of this. All of this leads to errors because in previous versions of DCS, the bomb's code could be programmed through the avionics, hence my confusion. The fuse types were removed in a patch, and in FMU-152, it was claimed to be configurable from the cockpit. I'd like to imagine that in real life it will be as you say. I've always been clear that this has never been possible in the F16, and this approach has been maintained in this aircraft but, in the F18, it's simply changed from one day to the next.
Conclusion: I no longer use the CODE button on the "weapons page" because it's useless. (I do use it in the TGP for LTD and LST because it needs tuning.
)
-
1
-
-
On 3/6/2025 at 10:18 AM, BIGNEWY said:
In the mission JTAC "AIRGUN" is 1688 and "LOPER" is 1711.
Can you confirm you set the correct laser code while on the ground in the rearm menu, and set it correctly when using the UFC?
edit: I've tested JTAC and all seems ok to me in my own mission.
thank you
P.S welcome to the forum
So, from what I understand, and I understand less and less, has this become just a label? (Red arrow in the drawing.)
A friend from the wing told me this, and I couldn't believe it. I set up the FMU-152 fuse, which is supposed to be set in the air, and it didn't work either. IT ONLY WORKS IF YOU SET IT ON THE GROUND. INCREDIBLE. Please put these drastic changes in mechanization in red letters on the ChangeLog.
-
4 hours ago, CapnCoke said:
To clarify, this only happens when MPD is in night mode correct?
Exactly, it only happens at night. I forgot to mention that this happens to me in VR (Quest 3 in my case; I don't know if it happens to other headsets) and with DLSS enabled (mode E). If I revert the changes and leave DCS as it originally was (green monitor), this doesn't happen.
My friend, don't worry about fixing it right now. Get your computer up and running first, that's the most important thing. I'm in no rush, and I'm very grateful. Thank you.
-
Hi @CapnCoke congratulations for this mod because I love it, I use it since it came out. The only thing I notice is that in Night Missions (dark whithout moon) the fonts are chosen becoming illegible as you have the shine up. To be able to read them I have to lower the brightness to the minimum and raise the contrast a bit. With the original fonts this does not happen. I do not know if you anticipate putting some kind of improvements in upcoming updates to correct the readability of the MDP at night or selecting Night mode.
Thanks for your work my friend.
-
1
-
-
yes, it's right my friend. I didn't think on this.I do not think this is the case, as you use NVPI to change the game profile, not the global profile.
Enviado desde mi SM-A336B mediante Tapatalk
-
But from what I understand, what it does is apply a common DLSS configuration (preset K in this case) to the entire computer. Or am I wrong?
Enviado desde mi SM-A336B mediante Tapatalk
DLSS 4
in Virtual Reality
Posted
Exactly, that's what I've been doing for a long time.
Does it bring any major improvements in DCS Ghosting?