warthog64 Posted June 2, 2009 Posted June 2, 2009 Just downloaded the F-35, and followed the download instructions exactly (Same as always) but for some reason the gun wont work. Any suggestions? Quote
+MigBuster Posted June 2, 2009 Posted June 2, 2009 Which F-35 are you using think the F-35B doesnt have a gun anyway - A defo should have - but the C not sure without looking Quote
+FastCargo Posted June 2, 2009 Posted June 2, 2009 Okay, I'm seeing this too many times to be just an odd glitch. First, ONLY the A model has an internal gun, the B and C use a gunpod. For anyone having issues getting a gun to show up I need the following specifications: Which version of the download, preferably a link to the exact download. Which aircraft. Which sim. Which patch. Also, I need to know, have you actually tried to fire the weapon in game. I've noticed in SF2 for some reason, the A model shows as having no gun ammo in the loading screen, but it fires just fine in game. FC Quote
Svetlin Posted June 2, 2009 Posted June 2, 2009 (edited) Hey, guys, just gave the F-35A a try in WOE and yep, no gun fire. Then I found a simple mismatch between gundata.ini record and F-35A_data.ini. The gun type is listed in gundata.ini as 25MM_GAU-22/A The F-35A_data.ini lists the gun type as 25MM_GAU-22A The difference is a mere slash "/", so I made the gun type in F-35A_Data.ini match the one in gundata.ini and now I have a firing gun May someone else give it a try to confirm if that solves the issue? Edited June 2, 2009 by svetlinnh Quote
+331Killerbee Posted June 2, 2009 Posted June 2, 2009 (edited) Also for the Ammo Amount Issue in the Loadout. It's a "Bug" in the Gun System. When TK made the Gun Editor for SF2, He left out this one Value from the Default GunData.ini. I don't know if adding them would solve the Issue. And I'm of the thinking that TK might have thought it would not be needed in "Merged" Data. These Values were supposed to include Gun Ammo Weight to the Flight charaterstics of the Aircraft. This is an Example from the Default GunData.ini below. But there are no Areas for these Values in the New Gun Editor. [GunData014] TypeName=20MM_M61A1 FullName=20mm M61A1 Vulcan Caliber=20.000000 ROF=6000.000000 MuzzleVel=1030.000000 AmmoWt=0.101000 AmmoStoreWt=0.308050 <<<<<<<<<<<<< This is it. WarheadWt=0.010100 Reliability=100.000000 Accuracy=50.000000 AddLight=TRUE MaxLightRange=1000.000000 FireColor=0.500000,0.450000,0.320000 GunFireEffect=20mmFireEffect GunFireSound=Vulcan EffectClassName=20mmEffects EffectTime=0.100000 TracerTexture=Tracer.tga TracerSize=0.150000 TracerDistFactor=0.002000 TracerLength=0.015000 MaxVisibleDist=4000.000000 MaxStreakVisibleDist=1000.000000 TimeFuzed=FALSE 331KillerBee Edited June 2, 2009 by 331Killerbee Quote
Guest a10boar Posted June 2, 2009 Posted June 2, 2009 WoV/WoE Oct 2008b F-35 A/B/C 2.2 latest weapons editor latest gun editor for 1st generation both placed in objects non-sub folders weaponsdata.dat and .ini is in weapon folder all weapons work as well as guns except for F-35A internal Use gunpod for B/C models Yes,test fired internal guns, nothing. Yes,checked F-35A_data.ini and gundata.ini and are correctly matching. It worked on old system but,not on new system. Quote
+331Killerbee Posted June 2, 2009 Posted June 2, 2009 Need to Check also if it has a Custom Gun Effect assigned to it. If it does, then adding the Effect to the GunData.ini like the WeaponsData.ini should solve that....... Quote
Guest a10boar Posted June 2, 2009 Posted June 2, 2009 Fixed issue with F-35A gun not working. A misread F-35Adata.ini vs. GunData.ini .I was looking at the gunpod and not internal gun for A model in gundata.ini. One is (gunpod) 25MM_GAU-12A and internal is 25MM_GAU-22A. Sorry fellas (cleaning glasses) Can we be friends again? Quote
Atreides Posted June 2, 2009 Posted June 2, 2009 Ver 2.2 SFP1 Oct 2008b. Got the internal gun working for the A using svetlinnh's method (Many Thanks bud). Checked weapons data and saved gunpod through latest weapons editor. Sadly still no gunpod on B or C. Quote
warthog64 Posted June 2, 2009 Author Posted June 2, 2009 Tried the "/" fix and it's fixed. Thanks for everyones help! Quote
+Dave Posted June 2, 2009 Posted June 2, 2009 I will get it changed it and re uploaded as soon at possible. I wonder why mine worked? Too weird. Quote
macelena Posted June 2, 2009 Posted June 2, 2009 I will get it changed it and re uploaded as soon at possible. I wonder why mine worked? Too weird. Perhaps you uploaded a older file wich you had saved before you made the last modifications to the package. If so, you should check for more things to fix, but if there is nobody reporting bugs, it shall not be as bad Quote
+Dave Posted June 3, 2009 Posted June 3, 2009 No that isn't the case. What I did was pull from the current pack and overwrite with new files. Just to avoid they very thing you just mentioned. So I have another disconnect somewhere. I will get it fixed though just need time. Quote
Svetlin Posted June 3, 2009 Posted June 3, 2009 Ver 2.2SFP1 Oct 2008b. Got the internal gun working for the A using svetlinnh's method (Many Thanks bud). Checked weapons data and saved gunpod through latest weapons editor. Sadly still no gunpod on B or C. My pleasure, mate! I did manage to get the pod loaded on the F-35C, don't remember to have done anything special. Will double check later tonight and will tell you how I got it to appear. Quote
Svetlin Posted June 3, 2009 Posted June 3, 2009 At Atreides: As promised, I checked my WOE install and the gunpod weapondata.ini entry. The only difference I noticed between the text provided in the V2.2 aircraft pack and the one in my weapondata.ini file is that I have checked that gunpod as exported: Exported=TRUE ExportStartYear=2008 ExportEndYear=2040 ExportAvailability=2 Apart from that, the usual procedure for adding a new weapon. So my suggestion to you is try to mark the gunpod as exported=TRUE and see what happens. Quote
Atreides Posted June 3, 2009 Posted June 3, 2009 (edited) Svetlinnh, word yo ! Thank you so very much, I now have GP's for the B and C models. Thanks again. Cheers. Edited June 3, 2009 by Atreides Quote
+Dave Posted June 3, 2009 Posted June 3, 2009 Well I also noticed that I do have a typo in the inis. As some stated. So I will correct that. Hopefully that will fix problems as well. [internalGun] SystemType=FIXED_GUN GunPortAnimationID=4 GunPortAnimationTime=0.2 GunTypeName=25MM_GAU-22A <------------------- InputName=FIRE_PRIMARY_GUN MuzzlePosition=-1.439,2.614,0.454 LightPosition=-1.439,2.614,0.454 AimAngles=0.0,-1.875,0.0 MaxAmmo=180 EjectShells=FALSE MinExtentPosition= MaxExtentPosition= [GunDataXXX] TypeName=25MM_GAU-22/A <--------------------------------- FullName=GAU-22/A four-barrel 25 mm cannon Caliber=25.000000 ROF=3000.000000 MuzzleVel=1085.000000 AmmoWt=0.180000 WarheadWt=0.018000 Reliability=100.000000 Accuracy=100.000000 AddLight=TRUE MaxLightRange=400.000000 FireColor=0.500000,0.450000,0.320000 GunFireEffect=23mmFireEffect GunFireSound=Vulcan EffectClassName=23mmEffects EffectTime=0.100000 TracerTexture=Tracer.tga TracerSize=0.150000 TracerDistFactor=0.002000 TracerLength=0.015000 MaxVisibleDist=400000.000000 MaxStreakVisibleDist=10000.000000 TimeFuzed=FALSE Quote
+Dave Posted June 3, 2009 Posted June 3, 2009 So I resized the one panel bitmap. Fixed the gun.ini's. Anything else anyone can think of? Quote
+Dave Posted June 3, 2009 Posted June 3, 2009 Ok re uploaded it. Someone check it out from the bottom up. Thanks. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.