Father Cool

Most beautiful plane ever made in my opinion.

True but I am all about this so hey. I also hate the look of all the new 5th gen stuff as well so there is that.

Haha. Nice livery though. I just think that it looks ugly regardless of colour.

I think the big reason to fly the F-15E over the F/A-18, which no one seems to have stated, is simply that the Hornet looks like crap and the Eagle is classic ass kicking sexiness. Arguments about arsenals are pointless in this fact, hence why I fly the Tomcat currently over the Bug in our Naval squadron. [emoji1787] Sent from my 2107113SG using Tapatalk

Yep and that's fine, I'm not expecting a fixed and dynamic for every livery. However the option of a dynamic modex skin that can be used as a basis for customs skins is better than none. The implication of a dynamic modex wouldn't be a major tweak of the model as it stands, its trying to get that to work with custom modex fonts and positions is the issue that HB currently have which, yes, is difficult to solve. A fixed universal location dynamic modex is not.

I get that but in the meantime surely allowing dynamic, as currently works with all other aircraft, with the option to not display one so that the baked in one shows through would be the best solution until they can crack the problem to their desired standard? Keeping something worse because you can't do it how you want is an odd way to think. I own a model manufacturing business where our products are aimed at being the most accurate and detailed models that you can buy however there are hundreds of things that we would like to be even more accurate but not possible with the current technology available, does that mean we don't bother making things? Of course not, we have to compromise where we have to until the solution presents itself later down the line. When that happens we will improve the models accordingly. HB can absolutely do this with the F-14 Modex.

A bit of a necro but relevant to my frustrations reskinning our squadron currently. I see what you are saying but tbh if you are flying in a group, and as we do in our squadron, with a fixed modex for each pilot i.e. I am 531 when in the cat, it is very important that we can see who is who when taxying around deck etc, or at an airbase for that matter, at a glance so the correct modex number is essential, whereas the font being correct and placed 100% correctly for a specific livery is of no consequence at all for us. We also run custom skins for our squadron but that bares no relevance to the issue at hand as even if we used prototype liveries then being able to dynamically change the modex is 1000% more preferable than having to have a completely separate skin set for every modex number of everyone in our squadron, which is the current state of affairs. I would take slightly incorrect modex position (fonts can be changed) over baked in modexes all day long.

Yes I know that, I could move it that way when I had the Lantirn mod installed however it would be good to use jester lantirn and when using Qhead just use a thumbstick instead.

Really like most aspects of the new Jester Lantirn except for one thing, I have a hell of a time getting the crosshairs on targets with Qheadlook. Is there a way to get Lantrin skew on a binding rather than wobbling my head back and forth and back and forth then up a bit then down a bit then back again and now too far and back again the other way and jesus arrrghh!

I am having trouble with exporting from Blender. It worked fine before but now it just says export complete but outputs a 1KB file with no model in it. Has anyone had this issue? Running Blender 2.93.

Agreed, i get this too. What gives?

Thanks great vid that however I'm not sure that can be done in MP with just a pilot. Also all of my previous INS alignment issues haven't been a result of excessive Gs etc, the one in that video above was on deck as I spawned with a hot start. It should have been bang on at that point however the WP1 steerpoint when I spawned in was at a given location, I entered a new steerpoint via jester from map, he entered the correct digits and when he was done the WP1 was still at the original location. He had done the programming but it wasn't selectable as the new location, not sure that its INS that's the issue here. One of my other INS issues has been on many occasions - fine align, take off, steady climb to altitude, program navgrid on route, switch to nav grid, all good, transit for 10 mins, navgrid now slewed off by several miles, keep watching navgrid, navgrid casually progressing across screen to one side, 10 more mins flying and now YY is like 600nm away from where it should be. Select a waypoint, waypoint now 600nm from where it should be. Switch to bomb mode and the drop line is horizontal rather than vertical. These things cannot be anything to do with the alignment process, it must be something to do with MP server alignment desync I reckon?

Well yes agreed, I do get it. Personally though I'd sooner die on landing after a successful 2h mission than fly out for an hour, end up being intercepted only to defend myself successfully, destroy the interceptor, resume course to find the INS shot because of an over G turn and a painful RTB with no objective even attempted. That being said I have never lost INS because of over G so maybe its all good. However I have lost INS in worse ways such as simply transiting the map, and even for using navgrid FFS. Those are/were bigger issues for me.

That's fair enough but I feel there has to be some compromise, there's nothing worse than transiting 150 miles to take out a ground target getting intercepted en route at 125 miles and having to take evasive action only to find that your bombline is now 45 degrees to the side because the INS is out meaning mission over and RTB.

Thanks buddy.

DCS-4YA_Cauc_Capture_Base_V3.0_ANAPA_OC That was the public one in the video I believe. Not sure which position I occupied though and not sure whether there's more than one carrier on there.

I agree with all of those points and that's my issue, I never said he wasn't entering them correctly I said the ones he entered weren't working when you select them. It appears that Jester inputs the correct figures but then when you select that input afterwards as a steerpoint it is not where it supposed to be. This is not every time and there seems to be no pattern. That example was a hot start on a public server, previously it was a cold start on a private server with an ASH alignment. Before it has also been cold start on a private server with a full alignment. Sometimes it all works just fine and there's no issue as all. You may think the issue is the alignment thinking the aircraft is in the wrong place, I did, however on the one above on the private server with cold start and ASH alignment the waypoints that were added in mission editor still pointed to the correct locations on the map whereas the Jester inputted ones were incorrect at the same time, that wouldn't be possible if the alignment was out. Of course the INS alignment is another issue completely and should never be out from the get go (knocked out by extreme g's etc during flight (although I think that a bit much personally as it adds zero play value) is another thing), I never ever shortcut the process (excepting ASH alignments which are added by our mission creators anyway and should work just fine) and always give Jester plenty of time to add in what he needs to when aligning or inputting waypoints etc.

Video showing the Jester waypoints not working.

The tests I did that didn't work orginally were cold starts from the carrier INS all ok, ME waypoints working fine. Added mybown as IP and ST. Not correct location. Testing again was on the same server same conditions as above, this time worked fine. Tried SP from airfield as well, all fine. Third try different online server hot start on carrier, added IP and ST, not correct. Added points as WP1 etc incase it was a ST thing still no joy. The fact that this is so hit amd miss makes planning our missions very difficult as we are never 100% sure that manually added waypoints will stick. Sent from my SM-A715F using Tapatalk

Yes I always give him enough time. He enters the numbers but the waypoint isn't where it supposed to be. Its not like this every time though.

Ok went online again last night and the issue returned. OMG I love the cat but jeez the nav system winds me the hell up.

Ok I just did several trials on SP and MP and all seems to be ok now. I will keep an eye out in future to see if there is anything amiss when it happens again.

It was a private server on Caucasus. I have it happen on all maps and servers though in the past.

Ok what info do you need? I go into F10 set a marker and call it say target, then in the Jester wheel select navigation and new waypoint from map, select Surface Target and then select the target marker from the options. Jester then taps away and when he's done I select surface target on my waypoints and Jester says ok and then the compass rotates to completely the wrong place and incorrect distance. This was in MP.

I have a problem where waypoints added to the F10 map and then inputted by Jester in pit are not correct. When I select them they appear to be miles away in the opposite direction. Waypoints added in the ME are working fine. Has anyone else had this issue?