Jump to content

laertesson

Members
  • Posts

    122
  • Joined

  • Last visited

Everything posted by laertesson

  1. I'm going to guess you're using Chrome. Try Edge or Firefox.
  2. Since a few updates ago, the dedicated server can’t be seen by me or friends after starting it (I have confirmed the port 10308 is open to outside connections to the server with yougetsignal, server and clients are updated and uPNP also on and it is visible on DCS active servers list, just not the server browser). Even IP connection doesn’t work, and I can’t even see it even though my PC and the server PC are both connected to an Ethernet switch. Any ideas to at least get my PC to see it, let alone anyone else’s? I even completely turned off the server’s windows firewall for a test and still can’t see it. we even tried hosting through both our clients and neither would show up in each other’s server browser.
  3. Hopefully Vulkan is truly coming this year and this mod will be deprecated. But in the meantime Kegetys is still the best mod!
  4. Thank you for the feedback. There is probably one more iteration before it is perfect.
  5. Not at all! I completely understand the apprehension to use mods, but I’m also confident RAZBAM will fix the issue officially, so no worries
  6. Here's a fun comparison I made really quick. I further adjusted value to -1.55. Altitude, dive angle, range to target, and speed are all quite close between these two attack runs, and both targets were engaged just as the pipper begins to unwind.. Sorry about the low quality, I'll try to make a better video on a full mission later. If you open in new window and zoom in you can see the target only takes one shot to explode on the right, and lefty never hits the target with the current code.
  7. Well obviously you’re not under duress to try my fix. If you’d rather wait for RAZBAM to acknowledge the issue, more power to you. Plus, ELMO changed this thread to investigating since I posted yesterday. So I really don't think you have reason to be nervous. I got tired of the broken pipper. My fix is not going to be enough for long-term since it doesn’t pass IC anyway.
  8. After testing in a mission with a few different max ranges entered, basically the pipper behaves as it used to before the adjustment of the gunpod in one of these last patches. Rounds land closer to the center of the pipper consistently with my modification, but I definitely want to hear what others have to say.
  9. It doesn't seem like it will affect other profiles because they seem to be in different lua files. For example the file I edited is only for the gun HUD. Am doing some testing missions as I type this so will report back. Thank you for the quick response and forward Elmo.
  10. Hi folks, I think I found a possible solution to this (which likely breaks IC), line 11 of Mods/AV8BNA/Cockpit/HUD/indicator/AG/AG_Page_01.lua reads: gun_boresight.controllers = {{"hud_waterline", -1.2 * HUD_SCALE}} I had a gut feeling that the 'hud_waterline' refers to the center X value of the boresight, and the second value is the Y. By adjusting the number downwards, away from zero, appears to pull the pipper's boresight up and thus fixes this repeatable error in the gun pipper. I have NOT done extensive testing, but a value of -1.45 gave me a MUCH more accurate pipper. Mileage may vary with speed, dive angle, who knows, I'd love if you guys could test this out. I've attached my file. Enjoy and please leave some feedback so I can further develop this fix if required. I'm no lua expert but seeing the frankly crass attitude of RAZBAM towards this issue, I figured I'd take a stab at it. No offense meant to RAZBAM, the Harrier is by FAR my favorite jet in the game, but the issue is kind of annoying and it's been around too long IMO. And it's nice to have my favorite weapon, the Equalizer, somewhat back in order! This should be on the user files soon if accepted under "GAU-12 pipper elevation fix v1". AG_Page_01.lua
  11. Hi guys, I'm a bit behind, is the original kegetys shader working correctly with current OB or do we need to use the Taz tree fix version provided by speed-of-heat? thanks for your help as always
  12. in my opinion features like this should have a special options toggle, at least until finished. it’s extremely hard to deal with in its current WIP state. just spent two days trying to diagnose this awful stick jitter back to center, literally seems more like a bug than a feature, would really like this one removed completely. Figured it must be a bug and rebound all of my controls twice
  13. This graph continues indefinitely - those single frame spikes to 30ms happen almost on a clock. I have diagnosed external processes extensively, and I watch Process Lasso like a hawk as the stutters happen and can't find anything that may be causing it. I have also relegated all processes related to VR to cores 4-7, and DCS to cores 0-3. Didn't help. I also reinstalled Windows completely to try to fix this, and the exact same stutter occurs again, with literally only DCS and drivers installed. I have no idea where to turn now. It's really frustrating that it runs completely fine at 5ms until the frame where it stutters. i7-9700K, 32GB 3200MHz, 2080 Ti. FPSVr screenshot below. GPU frametimes are solid during the spikes, only CPU.
  14. When I fly on the syria map, my CPU frametime will increase from <10ms to 35-40ms for a frame or two every few seconds. Other maps don't have the problem at all. I have tried the low terrain textures suggestion but the stutters continue.
  15. Hi, Much of the time when I go to download from the new DCS CDN there is a hard limit of 2.5MB/s, especially when downloading large files. It also likes to drop down to 0.0MB/s at times then ramp back up to the hard cap of 2.5MB/s. I just tested my speed while downloading and I have 120MB (NOT megabits) download speed so it's clearly a DCS issue. I am in the southwest USA.
  16. Yeah my -54s go dumb about half the time and all INS guided only want to drop really close even if I am high up.
  17. I don’t think this is a bug at this point, so I’d like to discuss when and why the TGP rolls the gimbal. It seems to do it a lot when I am close in to a target with a low dive angle. Anyone have strategies to avoid gimbal roll which makes the target become offset from the cursor?
  18. I ended up with day_color = {-0.05, 10, -0.05, 1}, gives a much more bright symbology without sacrificing color. thanks again for the negative values tip, seems to make the difference. I'll be looking out for your upload, I'm sure you could improve on this idea.
  19. Thanks, I am giving this a try. Is this the black HUD mod? Or those negative values give a darker green? This is really interesting. Thank you again Taz.
  20. With the release of A-10C II, I am having lots of trouble reading the A-10C hud against a bright sky, it gets almost completely washed out in my Reverb. As far as I know there is literally no way to adjust contrast or colors on NVidia cards. Is there a way now? I have tried even to change the materials of the A-10C HUD in the lua files, even that won't help. Brightest mode on the HUD used, OVR advanced settings doesnt seem to work, we cant use reShade, and NVidia settings offers no help. Seems like a really simple thing for MS to overlook for years.
  21. I always assumed air resistance moved them, I think I’ve noticed that before
  22. if you STBY then AG the pod, the first DMS right long designation won't drift. Youll have to STBY it again to avoid the drift in consecutive HMS designations.
  23. Yeah, kept happening to me each time I fly. Gonna have to wait for some sort of solution. I was definitely wrong about the rocket smoke thing after a couple more tests. Contrary what OP says I think this might be a new issue, I really don’t remember ever losing this many targets on my roll in. I also discovered that when you slave the TGP to the HMD more than once without setting it to STBY in between, the designation acts really funky and doesn’t hold a point on the ground.. if I hit STBY between attacks it seems to overall work better. Maybe it’s in the manual, not sure, but it seems weird.
  24. New theory for my issue: maybe it’s the smoke from APKWS covering up my TPOD track especially in IR mode. Makes it seem like the TGP has issues but I think it’s the smoke.
  25. It definitely only happened with maneuvering, and I myself didn’t look for gimb roll indications, but the OP did, and didn’t notice them. Gonna do some more testing on my own before uploading a track or anything like that.
×
×
  • Create New...