PeeJott17

Hello Ladies and Gentlemen. Finally we were able to release the VSN F-104C standalone in an early-access state (V0.99). You can get it here https://e.pcloud.link/publink/show?code=kZkMk6Z2ugmw0cKA0X0mMoNv8AboVB1hszV or, as an alternative, here: https://app.filen.io/#/f/e6c0639c-13c0-47e7-ba22-3a38964f4efc%23SyDSz5Wzl8lnQ4dTRXxd3DYOvHj4HPVf There is also a little "manual" that will help you find your ways around the cockpit as well as we've got one Test-Mission that tells you how to start the "Zipper". Cheers and enjoy the F-104C, VSN-Team.

That is the "missing-texture"-texture you've got there. I guess the outer part of the Gunpipper-Texture might be missing. It should be in Cockpit\Scripts_C\Textures...check if those are all o.k.. If not, try to get the damaged texture from the zip...

@Boelcke and @UN9249 Since I do not know which version you started with the VSN_F4, it is possible that you have started with a really early version, where the custom AGM-45s were in a seperate folder. Please check saved games\dcs\mods\tech. If there is a AGM_45 folder, please delete it. Use this hotfix Nr.2 to use the AGM_45 luas in the VSN_F4\weapons folder instead and everything should be "honky-dory" VSN_F4 HotFix Nr.2 2.9.14.207.zip

Great idea. Would love it

Hi guys. The recent bug with the VSN_F4 has been fixed (mostly). Use this hot-fix and there should be no more CTDs or missing vehicles. Cheers, PeeJott. VSN_F4 HotFix 2.9.14.001.zip

That would be just awesome. It would spare everyone soo much trouble. If you see what the differences are and can get some Info on the change, there could be a New version of the mod be ready for the release or earlier. So much less hassle for everybody. I would really like to test the stuff I'm responsible for for sure.

Hej buddy. That is a Glimmer of hope. I think it is totally clear that ED can't test every mod out there. Just a heads-up when a change is coming or when a bug gets mentioned that "this or that" was changed and could lead to the mentioned error/ctd would lead to solving the problem on both ends a lot quicker. In the end quicker changes from modders lead to smoother experience for the client -> less bug-reports -> less hassle for you and nineline. So everybody wins

Yes. I think it was the last bigger patch from ED that made me deinstall (deactivate was not enough) TacView since it halfed my FPS and led to lags and Spikes like crazy. TacView was not changed, DCS was. Then there was this mouse-polling-problem which added as a New feature a lot of lag and sometimes freezing pictures. My mouse and driver did not change, DCS did. I'm saying it is not understandable for me how such things can happen again, again and again. And regarding mods: Well, more documentation would be a start to know where to look for problems. The change-log does not really help, that is more for the players to see what was done. It really says not a lot where things were changed. Thanks buddy, that is a start.

The thing that makes me, well, ironically, more sad than mad is, that ED seems to have stopped to care about any mods and in the process the mod-maker-comunity as well. If you compare the list of flyable aircrafts (modules and 3rd-party modules) from 1.5.x to now I guess that will make it clear, that mods are not "needed" any more or something like that. I still don't really understand why ED does not appreciate the work, money, time and passion the modding comunity invests into their product. It is, after all, completely for free and enhances the experience for those who seek that enhancement. Normally you would think such a thing is appreciated and there is at least some form of information to what changes are coming and whether they might or definitely will infl+uence mods. The modders could (then) figure a work-around on their own, as soon as it is known, what has changed to what extent. If you just get an error or a ctd even with a long-log you might not get an idea what the real problem is. So you start the ever so cool trial-and-error process, where if you knew about the changes, that would not be neccessary. You would apply the changes where they are needed and everybody is a happy bunny...but I guess that is way to easy...

Yes, it is! ED is responsible for making their code not more fragile, but less fragile. How is it possible that every other new patch from ED is more and more unstable? Now it is custom weapons that are causing a crash, that was not there the previous versions. That is not good coding in my eyes. If you take a look at the log-files, it is ED's and 3rd-Party modules that throw one heck of a lot errors. That should be fixed. And always saying: It is the mod makers fault that they did not take a look in their crystal-bowl (yes, every mod-maker has one of those ready and at their disposal) and antricipate in advance what ED will do next and what they might feel like they would like to change and break in the process, is a pretty easy way of life. Sure thing, the mod makers spent money, time and energy for the comunity to bring assets for them for free, and it is their fault of doing so. Yep, that is 100% correct. They are on fault of doing that. May be the mod makers should spent their time rather on other stuff? May be building windsurf-boards or skis or whatever? There the "custom builder" can be sure that nobody is just going to make their freshly build windsurfing-bord or pair of skies unusable... But wait: If that were the case we would not have: - SRS - Tacview - BriefingRoom - WebMissionEditor - and on and on and on... Yes, it would be a better world for DCS users if just all mods would vanish instantly! P.S.: Sorry @rob10 for taking your post to heart and venting on it. I could have taken a lot of other ones that go in the same direction. Yours wasn't that bad at all, but I'm pissed since yesterday that ED, once again, made the modding comunity the present of having to do extra work to make something, that worked all along, work again... And there was, a year ago, a problem which looks to be similiar to this one:

Bei der F4 musst Du die Taste für Bugradsteuerung halten, dann wird das Bugrad mit der Seitenruder Eingabe synchronisiert. Wenn Du Fäden Button loslässt bleibt das Bugrad in der Position stehen. Also gedrückt halten, lenken, wieder gerade ausrichten, loslassen Bzgl der Waffennutzung werden die AtoA-Raketen über den Missle-Selector (schwarz-rotes drehrad links vorne) ausgewählt. AtoG-Waffen über das DogBone-Pannel (Hundeknochenartiges Panel genau hinter dem Stick). Links waffenart-selector und rechts stations-selector.

Yes, but not advisable... F-4B and F-4C skin-packs should sit right next to each other, here: https://app.filen.io/#/f/49a88f15-697d-403c-8efe-394dbc1b50e3#O1Urqqmi1YXC77e46E5qpzLjFF3jAzHc

Hello-there. F-101 is in our plans. Starting with RF-101C, F-101C and F-101B...but that is a ways down the road...

Hi. For the 105 we only have the Skins that come with the mod. A-3 is in development right now. It will have a stand-in twin-seater cockpit and an EFM, so carrier-operations will be possible. Right now all of my time goes into finalising the VSN F-104C standalone. Ince that is released, my attention will go to the A-3 (first EFM+FC3) and F-105D standalone projects... But one step at the time

Hi @yann59 How can I help you regarding VSN-Mods? Cheers, PeeJott.

You'll need to hop into the plane first which avionics are used. If F15C, put a F15C knto the Mission with late activation, hop in and change slots...done

May be I'm a bit stupid, but I was standing on Ramat David, tuned into TACAN Channel 84x, got the right bearing to the beacon but a range of 183 nm. My buddy got 0.0 nm that did not change during the flight. Neither did my 183nm. TACAN working properly on Caucasus and NTTR Range and Bearing. Any issues known regarding that or did I catch DCS on the wrong foot?

Honestly, I was only listening to the Operator from the Tanker. Since he did not say:"Your taking fuel." Or whatever he normaly sais and the basket slips away from the probe, it led me to believe it was not working no time to check the fuel gauge...to busy to keep the Probe in/near the basket...

@roobarbjapan and @R. Winters and @Reccelow I think we are working on something for you: Once we find the time, it will get an EFM and will be carrier capable. We would like to make the K-3 Tanker as well, but our tankers...well...they do not deliver any fuel. If you found the solution to that problem, we could finally make our KC-10 work as well, which would be great Cheers, PeeJott (from the VSN-Team).

Hi. Yes, it does work if you add a line of code in the F-15C entry.lua. Sadly that breaks IC. Cheers.

Hi. ATC and GCI (EWRs) are still not responding. This should get fixed. If you try to stay away from DataLink a GCI seems to je the way to go. But GCI without vectors or anything is not really helpful...

Hi. I just read the post right now. If you want to use SFM I have not found a possibility to have the external args connected to the Inputs without another lua driving the animations. It seems as if the connecting piece is missing. EFM drives the Animation on its own. Is there a fix for SFM as well?

@TKhaos Don't get me wrong, standalone mods are definitely better than FC3 based. The time to make them is a lot longer. A decent EFM standalone mod will take aprox. 2 years if you work on it with 2 people on the weekends or in the evening and you already own the external and cockpit model. FC3 SFM is about 3 Weeks with FC3 cockpit. About 2-4 months with custom cockpit, depending on how far you want to go. So only standalone will just lead to fewer mods and more abandoned projects. FC3 was also a stepping stone. If a mod found an audiance it made sense to develope it further and invest that time. There is not that much sense in developing a plane for two years to find out that nobody wants to fly it ;-)

Partly, because the external animations are gone. They need to be added by the mod-maker,but that is a doable task. Systems and flightmodel work the same as before.

Well, the only thing working without altering the FC3 entry luas is the change to PFM. When changing to PFM you more or less fly a A10A, SU27 or F15C etc. in a dress. The other road is a complete standalone version of the mod. There, you will have the limitations of avSimpleSystems (no guided AtoG weaponry, no TWS AtoA) AND it is a heck of a lot of coding work needed to code all the systems. FC3 was the only possibility to have a systems suite usable with your 3d external and cockpit model and an EFM, so it was a very good toolbox for mod-aircrafts that did not have to be that spot on regarding systems... That is why I really thank SkateZilla for his "Sherlock Homes"-Work and hope ED will just add that one line of code to 5 entry luas...should not be too hard or too much to ask