Jump to content

Shibiswag

Members
 View Profile  See their activity

  • Posts

    141

  • Joined

  • Last visited

Community Answers

1

See answers

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Shibiswag
    Well, that was the issue, I was trying to do a repair, and I couldn't without that error JSON error showing up. So apparently even to do a repair the updater still has to connect to the DCS server, so I guess now we know that if it's down, you can't do anything. That's why I was considering the re-install because I thought something at the core had messed up and wouldn't even allow it to repair itself.
  2. Shibiswag
    Confirmed, working again. Thank you BIGNEWY. Thought something was seriously wrong and didn't want to have to re-install.
  3. Shibiswag
    Game was working fine yesterday, now launcher crashes and can't even do a repair. Keep getting this error I haven't changed anything what so ever, don't want to re-install, how to fix? \AppData\Local\Temp\DCS\autoupdate_templog.txt 00000.000 === Log opened UTC 2024-12-10 04:37:50 00000.020 INFO : DCS_Updater/2.17.2.8 (Windows NT 10.0.22631; Win64; en-US) 00000.020 INFO : src-id: 1bc8e7517304bc62fa4e911299a74b67759f8a4a, lib-id: b88ea51ae2210987a3865f77cc1802548216d7a8 00000.020 INFO : cmdline: dcs_updater.exe repair 00000.070 STATUS: Initializing... 00000.071 INFO : basedir: F:\DCS World\ 00000.072 INFO : DCS/2.9.10.3948 (x86_64; EN; WORLD,CAUCASUS_terrain,MARIANAISLANDS_terrain,POLYCHOPSIM_SA342,KA-50_3,KA-50,MI-8MTV2,UH-1H,SPITFIRE-MKIX,BF-109K4,P47D30,P-51D,F-16C,A-10A,SU-25A,F-15C,MIG-29,SU-27,SU-33,A-10C,DEKA_JF-17,MIG-21BIS,RAZBAM_M-2000C,RAZBAM_AV8BNA,F-5E,HEATBLUR_F-14,A-10C_2,FA-18C,PERSIANGULF_terrain,SYRIA_terrain,NORMANDY_terrain,NEVADA_terrain,SINAIMAP_terrain,SUPERCARRIER,WWII-ARMOUR,CA) 00000.072 INFO : branch: 00000.073 STATUS: Checking for updates... 00000.797 INFO : Got reply from www.digitalcombatsimulator.com 00000.798 STATUS: JSON error: lexical error: invalid char in json text. <!DOCTYPE html> <html lang="e (right here) ------^ 00060.991 === Log closed.
  4. Shibiswag
    Refunded, used the money to buy the F4 instead.
  5. Mike Force Team started following Shibiswag
  6. Shibiswag
    Yes according to the Airforce it's 13m(40FT) I understand realism but even the accuracy is 80% within that CEP IRL However, f16 = 100% miss rate for all smart weapons, not just the JDAMS, but I did some plays online with the WMCDS and Brusers both go way past the PPSTP before releasing their bomblets resulting in a miss, though sometimes the bomblets drift over and dmg the target but still not good. So they need hopefully update it soon and add the two sub modes and tweak it on those or find some way to fix the INS of the 16. I mean I'm playing the 18 and the 15 so I don't have to worry about the JDAMS/OSM with those. Heck even went back to flying the good ol hog.
  7. Shibiswag
    So then why are 100% failing to hit their target when the coordinates are input in a stp in the 16? Yet the 15E which uses the same ##.##.### format, bombs hit 100% of the time and on direct target. the 18 as well even though it uses the ##.##.##.## format, still again, hits are 100% of the time. As well as the A10C1&2 This issue is specifically tied to the F16 in their last INS/GPS update. Something broke between the functionally of the GPS/INS system in the plane and the coordinates to the weapons. It's not just JDAMS, it's any guided munition aside from LGB, this includes WCMDS as well as the AGM-158 all weapons when put in via stp fail to hit their targets. Because if that's the case for the JDAM, this issue would present on all platforms that can carry it. Also why is it when i use the TGP in the 16 and creating mark points, they hit their target 100% of the time. Sorry I don't understand your logic. and it's actually 40ft (13m) according to the USAF.
  8. Shibiswag
    @Lord Vader Please see new track file I have attached regarding my previous statement regarding despite hot start, manual re-arming of mavricks are not BSGT from hot start. This is from a hot start - loaded Mav's on the ground via ground crew rearming, not in mission editor. I have done no attempt to BSGT in game as I did in the previous statement, as you can see targets are even 70+ miles away. When I near the target area you can clearly see the Mavrick seaker is not BSGT to the target pard and is slewed off to the right of the target. Only time Mavricks are actually BSGT to the TGP is as I previously stated only done when plane is loaded via mission editor onto a hot start, then yes they are BSGT and work correctly. MavBSGT-2.trk
  9. Shibiswag
    Actually, I have tested that. regarding the hot start auto-boresight. It only seems to work if the plane is pre-loaded in the mission editor, then yes, the mavericks are bore sighted correctly. Though not in the track file that with just a hot start and arming the plane, the mavericks are not automatically bore sighted and are still slewed off and not matching the TGP.
  10. Shibiswag
    attempted bsgt from the air, still did not work. Mavericks are still offset and Auto TGP handoff will not autolock due to the maverick being offset. Please let me know if I am doing anything in error. MavBSGT-1.trk
  11. Shibiswag
    Mavricks still do not work for boresighting, manual or auto. On the ground or boresighting from the air. They are always a few feet off to the right of the TGP. Only time Mavricks work with TGP is if it's a hot start with them already loaded then they are automatically bsgt and work just fine in auto or manual mode. Even if it's a hot start and they are loaded after, they will not BSGT correctly with the TGP, same with cold start. Until they fix it, BSGT is broken.
  12. Shibiswag
    Can we get a perminate keybind for the Ejection Arm seat. A user on here did one, can't find it now, but after the update it disappeared due to the config file being updated.
      • 3
      • Like
  13. Shibiswag
    Nope, same thing is happening to me, I already submitted a track, did coordinates correctly, even used the A-Fix function to make sure the Delta was only within a few feet 1-3ft yet bombs miss by a good 20-30ft. Every server I go into to ask, and all people confirm that they are all having the same issue with JDAMS using the 16. All other aircraft such as 15E and 18 work just fine.
  14. Shibiswag
    only happens in the 16. Using Created spearpoints for targeting and bombs always fall past the target. Yet when I run it with the 15E or the 18, bombs fall right on target.
  15. Shibiswag
    Thank you. okay thank you, I will try in an flight allignment for the mavricks. Also thank you for you're response for the JDAMs, though in question, The JDAM "Miss" only seems to be in the Viper. I have played that same mission with both the Strike Eagle as well as the Hornet. Both planes hit all 4 targets with PPSPT dead on. So this has to be limited to the 16 especially since the 15E uses the same 00.00.000 GPS format as the 16.
  16. Shibiswag
    apologies BIGNEWY. I wrote this out of frustration which I realize was in error on my part. It will not happen again, if you want, I will delete this post/topic. yeah, I can directly hit targets just fine with the 18 and 15E JDAMS fall right where they are supposed to. Just not with the 16. So I don't understand how it can work for some but not others. I'm going to try another test and input coordinates just shy of the target and see if that will result in a hit. The Strike eagle uses the 00.00.000 format as well in terms of GPS, so I can hit those same 4 targets dead on with the 15E in my mission. Yet with the 16 that uses the same 00.00.000 format bombs always fall past the target. So it has to be a bug with the INS somewhere still.
×
×
  • Create New...