unknown

Interesting, with the 442.74 driver the stuttering is nearly gone in the JF-17, not completely. But the fps drop with closing the canopy is still there for me. But thanks for that advise :thumbup:

The manual is stating the following: That would be a range of ~55nm and would match what you saw?

That is not entirely true, the Normandy map covers the Prime meridian(E/W).

I will post in this thread instead of opening a new one. I don't have performance issues in 2D, it doesn't matter if i use AG Radar or TGP or both. BUT, if i fly in VR(99 times out of 100) i noticed a stuttering every couple seconds, very annoying while moving my head. I noticed that in the JF-17 i get jumping fps between 30-40, average ~35/36fps (VR normal would be 40fps). If i start the same mission(time/location/view direction) in a different module(F-16, F-18 ) i don't get that stuttering and my fps are at 40 with some little jumps to 38 or 36 but without seeing any stuttering. I first thought this is related to the 3 MFD's but i discouvered they have zero influence to that. It is the CANOPY i realized today. If i start cold and my canopy is open everything is fine, fps at 40 like in the other modules and no stuttering, but as soon as i close the canopy the fps drop and the stuttering begins. I already deleted the fxo/metashader2 folders and did a repair(repair because of the 2 CTD i had over the last week). Any idea why the canopy is cousing trouble in the JF-17? If i takeoff and climb over ~4k-6k feet no problems again(stable 40fps) and it feels like in every other module, but down and on the ground i get stuttering/jumping fps again. I fly without mirrors. My settings:

Hi TrueGrit, the Newsletter stated: I would be interested to know how your team is composed. From that 15 people, how many coders(FM,avionics,weapons?), artists...are working on the EF-2000? Thank you in advance :beer:

They don't even know what version they will/can finally do, i doubt a december 2020 EA/release :music_whistling: But wouldn't be mad if they could pull that off :D

Ofcourse! :thumbup:

+1 This took me by surprise that it is not there. Also it would be great to have consistent behaviour of the hand controllers for us VR guys. I'm using the Rift S and use the hand controller to setup everything not mapped on my HOTAS. At startup for example i have to push the thumb stick forward/up to activate battery, ac and dc generators - so my physical hand/thumb movement matches the switch movement in the cockpit - both forward. But for other switches(for example taxi/exterior light) i have to pull my hand controller thumb stick aft/backwards and the switch in the cockpit moves foreward(opposite direction of my physical hand/thumb movement) and the opposite behaviour of the battery...switches. It would be very nice/convenient if this could be consistend for all switches matching my RL/physical hand/thumb movement. :thumbup: I know, this has no priority :beer:

1. No, Azimuth can't be changed with S2 in TWS. Manual page 73(see picture) 2. I don't know if this is supported by the JF-17, the only module i know for sure that gives you a warning to lower the gear is the KA-50 helicopter. I can't think of any other module doing this

No, the BRM-9 are laser guided rockets, you have to point a guiding laser(TGP) at the target. But if they are not moving and close to each other you can fire 2 missiles(couple seconds from each other, couldn't manage more myself), wait for impact 1 and slew the TGP to the next target and wait for impact 2. Maybe you could generate WPT's with the SPI copy/paste variant and slave the TGP to them for an attack with the BRM-9 but considering the relative short range of that rocket and the fact you have to guide them i doubt you will get more then 2 kills per pass, at least with my noob skillset in th JF-17. Edit: But multiple glide bombs released at the same time work perfect with that method. :thumbup:

Something i can test today, my approach to this was a little different, will test that :thumbup: Yes, my approach to store "target points" for AG weapons until now was to mark a SPI with the TGP(or radar), go to DST 40(thats where the SPI data is saved) and you can copy that into "pre-planned destination points" (for example 36, 37...), setup your weapons to the corresponding PP-point and you are good to go.

Lol and what exactly is holding off Eurofighter pilots to do the same? Learning their aircrafts pros/cons, teaming up with other Eurofighter pilots, train different tactics(together)??? What you write is true for every plane not only the JF-17! If you fight against a noob pilot in his shiny new toy and shoot him down where exactly is the reward in that?(arrogant pilots who think they are invincible because they have the newer toy are also noobs) Also i don't understand why everbody is now comparing their existing planes(F-14/JF-17) with the Eurofighter and how to beat it in MP air-quake battles? Just fly the aircraft you like to fly, it doesn't matter if it's the Eurofighter, JF-17/F-16, Mig-15 or what else, the only thing that matters is having FUN with it. But maybe i just can't understand your point because i don't like the "uncoordinated DCS MP style of missions(air-quake)" and my priority is SP. This is no offence against you, reading the posts just put a smile and a question mark on my face. So have fun :beer:

Works like advertised for me.

You have 3 options to choose from in the special options tab, while auto recenter is the default one. I rebind the arrow keys to the kneebord functions on all my planes so i didn't tried what the options do in-game.

I can't see why this should/could be an issue? First we had fighter of the 80's area(FC3)? Now we range from WW2 over Korea area to the 2007-ish or even newer area(JF-17)! But i agree with erverything else you said, i would prefer a as close to reality EF-2k as possible. And who knows, in 10 years we can have our T2/3... version ;) :beer:

I was flying the JF-17 all week long and had no problems until right now. I was flying my AG training mission again(like every day), this time i started in the FA-18, dropped Mav/bombs on target, returned to the ship, switched slot to the F-16, dropped bombs on target and returned to the airfield, tried to switch slot to the JF-17 and DCS stopped working, i didn't even get into the cockpit of the JF-17. This time the DCS crash app didn't start, i had to cancel DCS.exe via taskmanager, but the dcs.log is attached. The weird thing are these entrys?(and much more in the log) 2020-03-28 12:44:49.151 ERROR DX11BACKEND: Failed to create shader resource view for mods/aircraft/jf-17/cockpit/shapes/textures/jf17_cpt_sp_4_normal.dds. Reason: 2020-03-28 12:44:49.168 ERROR DX11BACKEND: Failed to create shader resource view for mods/aircraft/jf-17/cockpit/shapes/textures/jf17_cpt_sp_7.dds. Reason: Requested audio format unsupported. 2020-03-28 12:44:49.170 ERROR DX11BACKEND: Failed to create shader resource view for mods/aircraft/jf-17/cockpit/shapes/textures/jf17_cpt_fp_other_normal.dds. Reason: Requested audio format unsupported. For me that looks like it tried to load textures but was expecting an audio format ??? But i leave it to the experts to interprete these. dcs_log.zip

+1 I hope to see a "modern -ish" Su-27 Version, thats the bird that got me hooked back in the LockOn times and it's sad that after all that nice DCS full fidelity modules i seldom fly any FC3 plane anymore.

I played with the JF-17 for the last week and learned most of the systems, my main focus is AG. I run into the same "problem" that i fired AG missiles and the first hit the target and destroyed it while the second looked like it hit teh target but nothing happend to it. I did a quick test mission today on the Persian Gulf map. A couple vehicle/tanks moving on the street, locked them with the AG-Radar, switched to the 701 AG missile, slaved it to the AG target, locked the target, fired, locked the second target, fired and the first target was destroyed but the second one didn't even have a scratch. I saved the track and rewatched it, the TGP was not acurate in the replay but both missiles went for targets, the first hit/destroyed it the second looked like it exploded1-2m before the tank. I looked at the health bar of the remaining units on the F-10 map but all had full health. I watched the little test in tacview and there a hit was showed for both missiles but without destrying the tank(second target). I even did a test to look if that missile can destroy that T-72 from the front and that went well. Track and tacview files attached as zip file. ag_test.zip

I like your attitude :thumbup: Sums her up pretty well.

The problem is in the newsletter on the forum(at least for me), in the email there is a link to the screenshots.

That is a DCS problem and is true for all modules not only the JF-17.

My interpretation is every module with the $79.99 price tag on it.

Did you by any chance loaded the unguided BRM1 version? I was learning the JF-17 this week and the BRM1 worked fine for me.

My guess would be AvioDev. Edit: If it's not a new team. I'm excited for todays newsletter! :thumbup: