Jump to content

[VR] Jester menu has shifted left

Knock-Knock

By Knock-Knock
in Bugs and Problems

 Share

Recommended Posts

71st_Mastiff

71st_Mastiff

Posted
Posted

hence the reason we're open beta testing..

" any failure you meet, is never a defeat; merely a set up for a greater come back, "  W Forbes

"Success is not final, failure is not fatal, it is the courage to continue that counts,"  Winston Churchill

" He who never changes his mind, never changes anything," 

MSI z690MPG DDR4 || i914900k|| ddr4-64gb PC3200 || MSI RTX 4070Ti|Game1300w|Win10x64| |turtle beach elite pro 5.1|| ViRpiL,T50cm2|| MFG Crosswinds|| VT50CM-plus rotor Throttle || G10 RGB EVGA Keyboard/MouseLogitech || PiMax Crystal VR || 32 Samsung||

Link to comment
Share on other sites
RaTzo

RaTzo

Posted
Posted
Looks like they broke the JesterAI_Page.lua in the latest update. :lol: I reverted back to an older version, seems to have fixed it. I don't see anything immediately that I've broke, but who knows.

 

Location: DCS World OpenBeta -> Mods -> aircraft -> F14 -> Cockpit -> Scripts -> JesterAI

 

File is attached if you don't have it, it came strait from the non Beta version. Its in ZIP format so it can be uploaded here.

 

As always, use at your own risk, if you don't know what your doing seek help, etc etc etc...

 

RV.

 

Just quoting this workaround so that it doesn't get buried.

F-14B, A-10C,F-18C Lot 20, F-16C, UH-1H, SA342, Spitfire LF Mk IX, F-15C, Mig-29, Supercarrier, Nevada, Persian Gulf

 

i9 9900k 5.0GHz, 32GB RAM, 1080Ti, Rift S, Warthog HOTAS, MFG Crosswind pedals, Dual Monitors 4K & 1080

 

Every Day, Someone Uses Cute Krispy Snacks

 

[sIGPIC][/sIGPIC]
Link to comment
Share on other sites
-archer-

-archer-

Posted
Posted

Tnx RVator!

i7-6700k (4.7 GHz) // RAM 32 Gb // GTX 1070 // // Windows 10 64-bit LTSB;

VKB Gunfighter Mk2 Pro + VKB MCG Pro // BRD-F1(v.2) // Oculus Rift cv1 // BRD-N(v. №4) // VKB King Cobra MkII Fat // VKB King Cobra MkIII Fat // Saitek X55 // Saitek throttle Quadrant // Microsoft FFB 2 // Saitek X45 // Thrustmaster HOTAS Warthog // VKB MK20-3 Pro Pedals // VKB RDRXXI-L // TrackIR 5

Link to comment
Share on other sites
mytai01

mytai01

Posted
Posted

Not Cool...

MS Win7 Pro x64, Intel i7-6700K 4.0Ghz, Corsair RAM 16Gb,EVGA GeForce GTX 1080 FTW GAMING ACX 3.0, w/ Adjustable RGB LED Graphics Card 08G-P4-6286-KR, Creative Labs SB X-FI Titanium Fatal1ty Champ PCIe Sound Card, Corsair Neutron XTI 1TB SSD, TM Warthog Throttle & Stick, TM TPR Pedels, Oculus Rift VR Headset CV1, Klipsch Promedia 4.1 Speakers...

Link to comment
Share on other sites
Ratcatcher

Ratcatcher

Posted
Posted (edited)

#17 has the answer. (though not sure if Spalsh's problem is the same issue as others???)

 

How about stickying this thread and editing the first post with the necessary file?


Edited by Ratcatcher

Techlabs Chameleon Watercooled Gaming PC - Intel Core i7 6700K @ 4.7GHz : Samsung 950 Pro 256GB SSD, Samsung 500 gig SSD, Seagate 1TB 7200RPM Drive : MSI GeForce GTX 1080 "Founders Edition" 8192MB : 800W '80 Plus Gold' Modular Power Supply : 32GB (2x16GB) DDR4 PC4-25600C16 3200MHz : Occulus Rift S : TM Warthog : MFG Crosswind V2 : Win 10 64. PointCTRL.

Link to comment
Share on other sites
Jack McCoy

Jack McCoy

Posted
Posted

I looked at the modifications in the faulty file: refactoring along with changes in calculations for the menu position caused the regression.

 

I understand how complex it is to test DCS World in all its interactions but I wonder how this got through the cracks.

 

---

 

Reiterating previous post:

#17 has the answer.

i7-7700K@4.8GHz, 16Gb-3200, GTX-1080Ti-Strix-11Gb, Maximus IX Hero, Oculus Rift, Thrustmaster Warthog+F/A-18C, Logitech G940 Pedals.

Link to comment
Share on other sites
DERacing

DERacing

Posted
Posted

Too bad they didnt fix at least this issue in the 5/8 update.

Intel i7 9700k, 64GB DDR4 (Corsair), Gigabyte Z390 Master, RTX 2080 Ti AMP 11gb, 500GB Sabrent Rocket (System), 1TB XPG Gammix S11 Pro M.2 (DCS), Windows 11 64-bit Pro, Samsung 49" 4K CRG9 Monitor (5120x1440), Samsung Odyssey Plus, TrackIR 5, Thrustmaster Warthog Hotas, Various streamdecks, button boxes, Logitech Pro Rudder Pedals, Corsair K95 Platinum, Iron Claw mouse.

DCS OB, F-14B Tomcat, F-18C Hornet, F-16C Viper, A-10C Warthog, F-5 Tiger II, AV-8B Harrier, P-51D Mustang, FC3, Super Carrier
 

Thrustmaster Warthog Hotas, (3) Cougar MFD's, Logitech Pro Rudder Pedals, (2) Stream Decks, (1) Stream Deck XL, (1) Stream Deck Mini, Misc Button Boxes

Link to comment
Share on other sites
VC

VC

Posted
Posted
I looked at the modifications in the faulty file: refactoring along with changes in calculations for the menu position caused the regression.

 

I understand how complex it is to test DCS World in all its interactions but I wonder how this got through the cracks.

 

---

 

Reiterating previous post:

 

Because it's broken in VR only and testing is expensive. Testing everything essentially twice (on screen and in VR, which is a huge simplification anyway because there are different resolutions of both) is unrealistic, so they probably don't do it comprehensively.

 

This slips through the cracks in the same way a web designer might let slip a bug that makes text overflow and look bad in 1024 x 768 because they develop on a 1600 x 1200 screen and don't think to check.

VC

 

=X51= Squadron is recruiting!

X51 website: https://x51squadron.com/

Join our Discord: https://discord.gg/d9JtFY4

Link to comment
Share on other sites
StandingCow

StandingCow

Posted
Posted
Because it's broken in VR only and testing is expensive. Testing everything essentially twice (on screen and in VR, which is a huge simplification anyway because there are different resolutions of both) is unrealistic, so they probably don't do it comprehensively.

 

This slips through the cracks in the same way a web designer might let slip a bug that makes text overflow and look bad in 1024 x 768 because they develop on a 1600 x 1200 screen and don't think to check.

 

 

It's not only broken in VR, but multi-monitors as well.

5900X - 32 GB 3600 RAM - 1080TI

My Twitch Channel

~Moo

Link to comment
Share on other sites
Strikeeagle345

Strikeeagle345

Posted
Posted

have any of you guys downloaded the fix that was provide two patches ago? Have you read the this thread? The fix is in this thread...

 

Post #17 has the fix.

Strike

USLANTCOM.com

stepped_with_391_new_small.png

i7-9700K OC 5GHz| MSI MPG Z390 GAMING PRO CARBON | 32GB DDR4 3200 | GTX 3090 | Samsung SSD | HP Reverb G2 | VIRPIL Alpha | VIRPIL Blackhawk | HOTAS Warthog

 

Link to comment
Share on other sites
Eldur

Eldur

Posted
Posted
Because it's broken in VR only and testing is expensive. Testing everything essentially twice (on screen and in VR, which is a huge simplification anyway because there are different resolutions of both) is unrealistic, so they probably don't do it comprehensively.

 

 

It's not about testing. This issue has been there and it has been fixed already. It then came back as if an old outdated file made it back into the build that had been corrected already. But I see this phenomenon everywhere in software updates, literally. I also have seen this happening in projects I've been working on with multiple devs in charge. Sometimes fixes made by Dev A get overwritten by old unfixed files when Dev B submits his changes that may include the same files - but without the fixes Dev A made meanwhile.

 

 

Best thing in this very case is that we can use a workaround fix until the next update, thanks for providing the fix twilightsmile.png

dcsdashie-hb-ed.jpg

 

Link to comment
Share on other sites
71st_Mastiff

71st_Mastiff

Posted
Posted
It's not about testing. This issue has been there and it has been fixed already. It then came back as if an old outdated file made it back into the build that had been corrected already. But I see this phenomenon everywhere in software updates, literally. I also have seen this happening in projects I've been working on with multiple devs in charge. Sometimes fixes made by Dev A get overwritten by old unfixed files when Dev B submits his changes that may include the same files - but without the fixes Dev A made meanwhile.

 

 

Best thing in this very case is that we can use a workaround fix until the next update, thanks for providing the fix twilightsmile.png

 

That’s probably because they don’t keep a master build updated.

" any failure you meet, is never a defeat; merely a set up for a greater come back, "  W Forbes

"Success is not final, failure is not fatal, it is the courage to continue that counts,"  Winston Churchill

" He who never changes his mind, never changes anything," 

MSI z690MPG DDR4 || i914900k|| ddr4-64gb PC3200 || MSI RTX 4070Ti|Game1300w|Win10x64| |turtle beach elite pro 5.1|| ViRpiL,T50cm2|| MFG Crosswinds|| VT50CM-plus rotor Throttle || G10 RGB EVGA Keyboard/MouseLogitech || PiMax Crystal VR || 32 Samsung||

Link to comment
Share on other sites
Kaiju

Kaiju

Posted
Posted

Download JesterAI_Page.lua file and copy/paste it in :

 

C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F14\Cockpit\Scripts\JesterAI

IN WIN D-Frame Red - EKWB - Asus ROG PG348Q - Asus Maximus XI Formula - i9 9900K 5.1Ghz - Asus Nvidia Geforce RTX 2080Ti Strix OC 11Go - DDR4 Corsair Vengeance LPX 64Go 3000Mhz - Windows 10 64 - x2 SSD PCIe M.2 NvMe Samsung 970 Pro (1To RAID 0) - Virpil V.F.X Grip and MongoosT 50CM2 Throttle - Thrustmaster TPR - HP Reverb

Link to comment
Share on other sites
LASooner

LASooner

Posted
Posted
Same or me in VR

It is set off to the left like first picture.

It works 100%, just offset.

 

Fix:

https://forums.eagle.ru/showpost.php?p=3892202&postcount=17

F-14B, F-16, F-18C, A-10C, F-5E, F-86, FC3, BF-109, FW-190, P-51, Spitfire, UH-1,AJS-37 Viggen, MIG-15, MIG-19, MIG-21, AV-8B Harrier, P-47D

Persian Gulf, Caucuses, NTTR, Normandy, The Channel, Syria

Combined Arms, WWII Assets,Super Carrier

TM Warthog, Virpil VFX,BuddyFox UFC, Saitek Pro Flight quadrant & Switch Panel, Odyssey+ VR, Jet Pad w/ SSA, Voice Attack w/Viacom Pro

GeForce RTX2080TI OC, Intel Core i7-7700K 4.5Ghz, 64GB DDR4, Dedicated 1TB SSD

Link to comment
Share on other sites
VampireNZ

VampireNZ

Posted
Posted

Pretty bad form for HB/ED to have ignored this for so long. I just performed an update after not flying the 'Cat for a while and totally forgot about this...till I was in the aircraft and opened Jester menu - "oh yea....FFS"

 

Obviously for most computer literate people locating and swapping over a file isn't a big deal - but not everyone is comfortable delving into the folders and swapping over files etc on their computers. Whenever I go home I have to do a bunch of stuff so my dad can keep playing his flight sims as he is not comfortable at all doing that stuff.

 

For game breaking bugs like this there really needs to be an official update sorting it out. You literally can't use the Jester menu without the fix.

Asus Maximus VIII Hero Alpha| i7-6700K @ 4.60GHz | nVidia GTX 1080ti Strix OC 11GB @ 2075MHz| 16GB G.Skill Trident Z RGB 3200Mhz DDR4 CL14 |

Samsung 950 PRO 512GB M.2 SSD | Corsair Force LE 480GB SSD | Windows 10 64-Bit | TM Warthog with FSSB R3 Lighting Base | VKB Gunfighter Pro + MCG | TM MFD's | Oculus Rift S | Jetseat FSE

 

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites
  • 1 month later...
valleyboy

valleyboy

Posted
Posted

Still having this problem in VR.

No matter how many times I ‘fix’ it, next mission start it’s broken again... Jester menu is shifting to the left.

Yes I replace the lua, delete it, repair etc. Problem still comes back.

 

Is it related to vaicom pro at all? As realised that interacts with the specific lua, If I set lua to read only vaicom wont run.

 

Anyway, anyone else still with wonky Jester?

Link to comment
Share on other sites
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...