PeeJott17

Hi everyone. I'm loving the map, but the borders seem to be off in hight-map. They look to be good on the normal map. Here are some screenshots:

Big thanks @SkateZillafor finding that solution. Fingers crossed ED findsvthe time to add that one line of code to the FC3 planes in the next patch

Sorry guys, wrong Info. I need to check this patch, but the last one still needed a change in the entry.lua of the FC3 planes to access the 104 FC3 EFM Version...

Hi. When did it disappear? Did it work before? It should have been there but harder to access. After the last patch, the F-104 should be "back to normal" since ED "patched" the problem, thankfully.

@opsyou are a magician. Got it working with your ideas for A-10A avionics like this: MAC_flyable('VSN_F80C',current_mod_path..'/Cockpit/A10A/',{'A-10A by Eagle Dynamics','A10A', old = 17}, current_mod_path..'/comm.lua')--SFM Now I need to find a way how I can use the FC avionics-pack with an EFM-Mod...than we are back to "old form" :-)

@SkateZillaawesome work. Did you test those entries as well regarding EFM-mods: -[[ DEFINE EFM CFG PATH ]] --local cfg_path = current_mod_path .. "/FM/F22A/config.lua" --[[ DEFINE EFM DO FILE ]] --dofile(cfg_path) --[[ DEFINE EFM SELF ID ]] --F22A[1] = self_ID --[[ DEFINE EDM BINARY ]] --F22A[2] = 'F22_EFM' --[[ DEFINE EFM CFG PATH ]] --F22A.config_path = cfg_path --[[ DEFINE EFM OLD VALUE ]] --F22A.old = 6 -- SU27-3, SU33-4, F-15-6, SU25-54 --[[ DEFINE F15C EFM CFG ]] --local cfg_path = DCS_ROOT_PATH .. "/FM/F15/config.lua" --[[ DEFINE F15C EFM DO ]] --dofile(cfg_path) --[[ DEFINE F15C EFM ID ]] --F15FM[1] = self_ID --[[ DEFINE F15C EFM BIN ]] --F15FM[2] = 'F15' --[[ DEFINE F15C EFM CFG ]] --F15FM.config_path = cfg_path --[[ DEFINE F15C EFM OLD ]] --F15FM.old = true Do we just need to define F15FM.old = 6 before we define the mod as before: (may-be like this?) local cfg_path = current_mod_path .. "/FM/F22A/config.lua" dofile(cfg_path) F22A[1] = self_ID F22A[2] = 'F22_EFM' F22A.config_path = cfg_path F22A.old = F15FM -> that can not work! May be F15FM.old??? Just thinking "loud".... But it will not work since the ID will be wrong for the F15CCWS.DLL. I guess it needs to have as ID 'F15C" and not "F22A"...

Ohhh, a round of applause for @SkateZilla Will try to confirm that works this evening

Well, I know since I'm part of VSN as well. The problem is not that FC3 has gone away, the problem is that it seems (I can't be 100% sure since I can only read the errors presented and make something useful from it) as if it is now forbidden for not FC-Planes to call FC-Avionics-Pack. It wasn't like this before. The HotFix did not "fix" this situation so it might be a "feature" of DCS 2.9.6 or it was a coincidence and is far down the list of things ED might want to address "in the future" or may-be never, who knows. Anyways, I hope somebody bright comes up with a good idea, since otherwise we will have to Code our own avionics-suit which will take a lot of time and will fall short, functionality-wise. So a "lose-lose"-situation, sort of (not so much for my beloved early cold-war planes, but anything from the mid 80s onwards will be severly hampered).

Hi there. We are in the development of a standalone-version of the F104C. What we have so far: - cold-start (100%) - radar (85%) - gunsight (85%) - weapon-system (80%) - simple electric-system (100%) - cockpit restructure for C-Version (35%) - cockpit animation (60%) - clickability (45%) - Radios (45%) So the "zipper" will be around, even if FC3 really has closed it's doors for mod planes.

Hello guys. The last HotFix was not so hot for FC3-based mods. It looks as if this "problem" might not have been a bug, but may-be a feature? I don't know it of course, but if it was just a coincidence it would be awesome to get a little push in the right direction. Trying, retrying and trying again to make something that always worked, work again is a bit...well...time spent for nothing really. Every Modder would rather spent the time on her or his mod(s) to enhance it and make the DCS-Experience cooler and even more worthwhile for everybody. Right now I try new ideas as well, but it seems more and more like time wasted...the good thing us, there are a lot of guys more talented and I hope they will find a way where I might find...nothing...

Thanks for the heads-up. My problem solved itself through deinstalling TacView and setting the mouse too 500 Hz polling-rate..

@SkateZilla did you try loading the F15.dll and F15ccws.dll through the entry or another scripts-file from the original place (from the installation path from DCS)? They can not be loaded when in the saved-games folder but should be loadable from the original path... I guess... only idea I have so far...

Well, yes and no. ED changed with FC2024 the loading-behaviour of the FC3 aircrafts. So every mod that was based on FC3 (which are some) gets problems, since the avionics pack is not preloaded anymore. You will have to load the avionics-pack manually by entering a F-15C before entering one of the mods that use F-15C or any other avionic. It will even work with an F15C set to "late activation". As soon as the avionics-pack is loaded, the mods work normal. That is a bit of a let-down for the modding comunity, especially those who need to use FC3 as a base...may be they change it around with the hot-fix for FC3..who knows...

Hi. I have an identical problem. GPU at 30-55% and CPU around 34% with 30-40 FPS. Makes no sense at all. Before the update I had with the same settings wit VSync always 60 FPS and theoretical above 100... There is just the new install? That is not too cool... Cheers, PJ

You are sooo spot on @Gogi12 ;-) And another cool video from @Spino who really nails the use of the early Six pretty darn good in his vid. That makes the reason the "Six-Shooter" project was initiated pretty clear, even more so when you add the "lessons learned" from Vietnam dogfights:

Hello there. We just released the VSN F-106 DeltaDart. A FC3 based EFM mod with a custom pit. If you like, you can take a look here: and download the mod right here: https://drive.filen.io/d/453c8ea1-f087-467a-890f-952786fa7915#i6EWVHo5tJFQdrEjts3Lt0mshDXn4GTz SkinPacks, thanks to Urbi, can be downloaded here: https://drive.filen.io/d/4e2d334a-4054-464d-bac2-34cb9d4311ba#jCgBsLioSt33RN8RqzWOwiAo3n8CuCpx and here: https://drive.filen.io/d/29c5db68-4846-4077-b65b-7ef705fa361e#p72Di64FhF9Wvak62UpCltFJt65FfWDp Big thanks to JP-Ferree for the cool trailer and the menu pictures, Pallino66HD for the soundtrack and Phil from Virtavia.com for getting us a license to use the really cool model. If you are into DCS-modding, you will find the source-files for the EFM in the download. Please keep in mind, that the VSN_F106 EFM is based on the VSN_F104 EFM (except of course the data for aerodynamics) which is, in some parts, based on the A-4EFM. You are free to use this EFM or parts from it, when complying to the GPL-3 licensing agreement, which you'll find there as well.

Hhhmm, how do I say this: "The spirit is willing, the flesh is weak." and "Tempus fugit" Kind of... Be asured, that we really, really want to make the Thud a DCS reality, but...well... see above...

@Comrade DogeThis is one piece of very cool software. Thanks a lot. Makes waypoint-editing sooo much more fun (and a lot less painful). I was wondering how you transfer the waypoints into the planes systems. I'm one of the Devs from VSN and your App would come in very handy for our F-4B/C and upcoming standalone Mods for multiplayer use. Right now, we are reading the waypoints from the mission itself. Is there a possibility to read the waypoints from TheWay somehow? It transfer the waypoints somewhere and I guess they do not get set in the mission itself?

Yes. I know, I want it to, but "busy-busy-busy"....

Well, yes and no. We will be releasing quick-patches from time to time. We will try to gather them after a while into one bigger Patch (see above). After substantial changes we will release an updated complete mod. I think it is not too hard to follow and, very frankly, if it is too much "work" to figure out which patches are needed...hhhhmmm...How will the learning part of a New aircraft will go? I guess it will not be too satisfying...

Here is the complete Update for the F-4 from V 2.8.4.200 to V 2.8.7.204: https://e.pcloud.link/publink/show?code=XZBkhnZa0EhpCBTL2X9CUIzmmn6dLilGNt7

Nope, they are not. You need x.x.x.200 x.x.x.201 x.x.x.203 and 204.... Just pretty straight forward I would say. We are not making everything a "new" mod since it is zipped 1GB download...no use downloading 95% stuff that has not changed...

Nice and enjoy the Lightning @Rudel_chw

You have a very valid point here. I'm already excited to see how the new "comunity mod" will behave once it is released. I'm especially interested regarding systems-modeling (Laser and GPS-Weapons on a standalone mod??? SDK anybody ) But anyway, I whish those guys the best of luck and hope they can deliver a good version of the Lightning-II.

Aloha les amis. A little "life-sign" from VSN. Here is the slightly updated VSN F-35 Lighning II (Ver. 1.9.1.103) with slightly tuned EFM and some added changes: EFM: - FBW switch (and Input/Command) added, which swiches FlyByWire on and off (you might want to leave it on) - changed pitch behaviour with FBW-ON (very slight pitch down, almost stable att-hold) - changed flight-behaviour in FBW-ON (I guess more like a lot of guys expect it to be) - camera-shaker slightly reduced - higher AoA in FBW-ON mode possible - changed bahaviour of VTOL-Mode for F-35B (added pitch-thrust for more stable flight) MissionEditor/Statics: - F-35 gets displayed with open Bay-Doors to see what yo are loading onto it F-35C and Carrier: - problems remain. Cable gets caught, but does not slow the plane down enough. SuperCarrier no response from DeckCrew: Force "Hook-to-Cat" is possible by rolling onto the cat, lowering the launch bar and pressing the "Hook-To-Cat" command more than once. Cat gets "fired" when reaching AB-RPM. (If somebody finds the cures to those problems, let me know and I'll update the mod.) https://drive.filen.io/d/75b7b60d-b94a-485d-bef0-2b7d2f3cf447#10i7zdbhjeYYFaGRezYlTPINyC2SR3Pt Since there is a comunity-F-35 Lightning II in the making, that will be a lot better than ours (if you can trust the devs), we will (most likely) halt the developement of the F-35 here. There is no use in developing the exact same plane in parallel, since somebody will eventually waste his or her time doing that, and time is to precious to be wasted. Cheers and enjoy the plane, PeeJott.