VIXEN413

Hey guys, Quick question, Anyone with Intel on Sam and radar sites in late 50's, early 60's? Sabre LABS bombing mission in the making... Need info. Also, any info on "fruitset" and " spoonrest " radar sites?

Ooh boy, now that we have the CWG map, that bird would fit in perfectly.... The Streak was used by France, Belgium, the Netherlands, Danemark, Germany(west) and Italy.... My dad flew it in the Belgian air force out of EBFS late 50's, early 60s, they were atomic strike, ready to plant those big atomic mushroom clouds in Magdebourg area using Labs bombing... any chance an f84f could become a reality as a module? BR

Hey Urga, The map is awesome! Thank you so much Phase 3 will see Liège (EBLG) added.. Here are some pics taken late 80's. Notice concrete state on the runway and on short final, the remains of the old WW2 airport ramp and old tower. BR

Hello all, just transitionning from a G2 to a Cristal light... installed the whole lot yesterday. I ve installed the Pimax tool app, the openxr pimax runtime, I had already open xr toolkit for the G2 so I just reseted all settings, I m also usig the quadview companion. I ve been using these settings and values for my 3080ti (altough here, it's for a 3080) All in all, got myself in a good spot and it's running awesome in clarity and frames.... Happy camper, well, almost.... While in-game, there is a sort of square, in front of each eye, where the image looks to have a different tint. Just like if there was a filter applied or a ghost "see trough" kinda box from another app, not quite sure what it might be... I tought that with the added clarity, I was seeing the jhmcs reflection zone where the helmet can project the data in the hornet (but unlike the apache it is not a modeled thing in the f18) but older planes also have it.... Is it a local dimming thing? or the frontier between the LED/QLed Panels? or quadview playing tricks?. Any idea? best regards

I found a hardware fix that I m happy with... up to you guys to try if u like it. As I said, the real TDC in the jet is an OTTO force sensing ministick. Apply a little bit of pressure to a direction and the cursor will move slowly but apply a lot of force, your cursor will run like in the video above. Most of our throttle have ALPS ministick (just like playstation sticks) that are based on angle to provide a deflection. They have short arm and lots of angle so it's mega easy to overcontrol them. With previous TDC speed I realised I was almost always bumping them to full deflection witch is not the way it should be. So on my winwing tdc ministick, I set the curves to 0 then popped out the cap to place a roundel of foam underneath. I had to find the right thickness so that the cap would meet resistance while moving. took me 2' but you can take out that cap super easy... It allows for good smooth movements near the center for more precise work and, by applying more force, you can still get the fast cursor speeds. It's also closer to the feeling offered by a force sensing ministick... For Virpil throttle, the cap is different so you ll need a different way to place some orings... hope it helps

in the Hornet, the throttle grips are made by Mason industries and use OTTO switches allround. the TDC is a non moving (or barelly moving) force sensing ministick (look for it, U can buy it on Mouser for 750USD). Now, the way it works by registering force applied giving as a result a cursor speed movement makes sense for the sensitivity U have from such a device. U can be precise like that. TDC on Virpil (CM 2and 3), winwing f18 throttle or also Thrustmaster mod for the tdc will all use ministick like the ones U find on xboxes where, due to the deflection and moment arm, it is very difficult to be precise around the center and you will overcontrol almost everytime... That's why this change has made Cursor operation on our hotas way more difficult... the speed and sensitivity of the TDC now in game does not fit with harware on sale for home sim use... I worked around the issue by using 60-70% curves on those axes to slow it down near the center to keep a bit more dexterity but even then it's harder the it used to be... the real fix is the 750$ OTTO ministick... Right...

Hey there, as per title, It seems I cant get the ddi buttons to animate when I click on them. AMPCD buttons works great but DDI pb dont move anymore when pressed. On the UFC, all buttons move when clicked except the I/P button (but action is registered in the control assignment) Anyone else noticed this behaviour? Same in OB ST or MT... BR

True that but even if it plays with bigger angle and more bars, it is still a reduced scan volume... should not take that much to complete a full swipe of the area, no? can any SME give their thaughts on this? BR

Hey there, I think the fact that I can get an ACM lock earlier or later depends on target track generation and it is linked with the bug discussed here as well about how the mission computer generates those tracks. first recorded game track I got WACQ lock at around 3Nm and on the second one just around 8Nm. Dunno, it seemed inconsistant today in general. I noticed that, usually when I recommit after a skate or abort, the hafus are dissappearing then reappearing on the ATK RDR and just as they reappear, I guess the mission computer regenerates the track and then I can get a WACQ or ACM lock. By the time, the 10NM mark is past for a while. Irony is that I have a tally way before it gets me an ACM lock... late WACQ.trk late WACQ2.trk

Noticed that WACQ does lock stuff up only around 6-7 Nm... was it not supposed to be able to do the job on a fighter sized pkane up to 10Nm? BR

Hey there. Yes, I do fire the HARM but only after I do the reset of the A/G mode. look at the bezel of the left DDI after I release the JSOW I try to change the weapon from J82 to HARM or RT by pressing pb7 and 8 but nothing happens, you see on the screen the button clicking physically but the page is stuck. on this track, I try many times before finally resetting A/G and then I m able to select HARM weapon page and fire them

Hey there Bignewy, Thanks for looking at it. Indeed, I just setup a quick mission but still had one unit from the high digit sam mod. I ve redone it with SA11 BUK so you ll see what I mean. So again, same deal, a 360° to setup the JSOW (still with the target elevation issue as mentioned in another bug report too) and an ingress to target, popup and release all 4 JSOW, I roll inverted then back in normal flight towards the SAM site. At this point my stores page is still in the JSOW sub page and when I try to click on PB7 or PB8 for HARm or RT, the page does not change. Either by using the mouse or with my DDI button. I need to recycle A/G mode to "unbrick" the stores page.. Hope you can view the trk now and see what I mean. Thanks Best regards stuck.stores.page.trk

Here are 2 tracks showing the issues. I ve quickly redone the mission with ingame standard sa10 iso the high digit sam. First track is extracted from flight in VR so that might not be the easiest to check but the second one will show the issue too. On both tracks, I start with a wide 360 to setup the JSOW and can reproduce the elevation bug when WP designate (it's also part of another bug report). Then I proceed to ingress, popup and release the glidebombs and I want to click to the HARM or RT weapon on button 7 and 8 and nothing happens. I m using MFD's and the input on the bezel is registered as you see the button clicking on the screen, same if I use the mouse to click on it. Workaround as you can see is to get out of A/G then back in and then click on button7 for the HARM (I later get teh Pullback message on hud so I know technically, I dont need to acces the page to shoot it in SP but all this is prior hud messagel. SA10.trk stuckstorepage.bug.trk

got a chance to test it again, and indeed, the bug present itself each time you edit a WP elevation in FT and then designate/undesignate that WP for weapon useage (in this case a JSOW). It seems to divide the altitude by 3 each time, just like if it was a conversion feet to meters. Also, when you have a WP set with an elevation in feet, upon designation, it shows in the "mission" sub page of the JSOW/JDAM but converted as meters. It should indicate feet there as well IIRC. If the WP elev is in feet, it feed the mission page in feet and if in Meters, it feeds it in meters. But now, it looks like any WP, with it's elev either in Ft or M, when designated, will be converted in meters in the JSOW mission sub page and if you send over an altitude in feet, it divides it by 3 to convert in meters.... Work around is to work in Meters only but still, annoying bug lol tgt.deg.alti.bug.trk

looks similar to the issue I reported in the JSOW bug, related of designating/undesignating...