Jump to content

Recommended Posts

Posted

Just got the latest patch installed and it looks like the navigation system isnt working as it should. Maybe its just me and ive missed something. After takeoff, waypoint B1 is west at about 300 even though the actual waypoint is on a heading of 60 say. Anyone else having issues?

  • Like 1
  • Thanks 1

Youtube channel @Flightenvy680

 

Banner 1.png

Posted (edited)

Waypoints created in the mission editor are not loading. As a workaround for the moment you can use cartridges created from the F10 map, or using the .ini files. They seem to be working correctly.
The bug has been added to the HB bug tracker.

Edited by MYSE1234
  • Like 1
  • Thanks 2

Viggen is love. Viggen is life.

7800X3D | RTX 4070 Ti S | 64GB 6000MHz RAM |

Posted
1 hour ago, MYSE1234 said:

Waypoints created in the mission editor are not loading. As a workaround for the moment you can use cartridges created from the F10 map, or using the .ini files. They seem to be working correctly.
The bug has been added to the HB bug tracker.

 

You can also of course input the COORD's manually using the REF/LOLA function. There'll only be max 9 points plus maybe a couple BX's. I believe the old AJ version had to do this anyway prior to the data cartridge. So kinda the most realistic. I hate the F10 method.

Posted (edited)

Ah this would explain why the training missions I tried don't work. I thought I was doing something wrong navigation-wise.

Any chance it could a DLL 'meet me in the alley' fix, rather than having to wait till New Year for a ED hotfix? 🙂

Edited by fearlessfrog
Posted
36 minutes ago, fearlessfrog said:

Ah this would explain why the training missions I tried don't work. I thought I was doing something wrong navigation-wise.

Any chance it could a DLL 'meet me in the alley' fix, rather than having to wait till New Year for a ED hotfix? 🙂

 

yeah I really hope we get a hotfix before ED is out for the Holidays otherwise I feel like we're going to be sitting on this until late January I'm afraid.

Posted
40 minutes ago, Hawkeye91 said:

otherwise I feel like we're going to be sitting on this until late January I'm afraid.

 

You can always undo the update and revert to the previous version of DCS.

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted
1 hour ago, fearlessfrog said:

Ah this would explain why the training missions I tried don't work. I thought I was doing something wrong navigation-wise.

Any chance it could a DLL 'meet me in the alley' fix, rather than having to wait till New Year for a ED hotfix? 🙂

 

Latest for a hotfix is likely next week. More info when we converse with ED further! Sorry for the wait.

  • Like 7

Nicholas Dackard

 

Founder & Lead Artist

Heatblur Simulations

 

https://www.facebook.com/heatblur/

Posted (edited)
18 hours ago, funkstardeluxe said:

I am learning the plane and I thought I was doing something wrong...I'll keep flying visual for now!

Same here, got the viggen after the beta patch. Watch videos over and over again.  Could not understand why it didn't work.

Edited by Gunfreak

i7 13700k @5.2ghz, GTX 5090 OC, 128Gig ram 4800mhz DDR5, M2 drive.

Posted (edited)

I am just getting into the Viggen when I found out about this issue.  Could someone explain to me how to do waypoints for the Viggen in the F10 map while in the jet?  Also where is the init file that you can modify for waypoints?

Thanks

Edited by sobe

Trackir4 using the latest Trackir 5 software, Win10 Pro [Creator Update] updated from Win7Pro Pro 64Bit, Intel® Core™ i5-2500 3.30 GHz 6M Intel Smart Cache LGA115 , GigaByte GA-Z68XP-UD4 Intel Z68 Chipset DDR3 16GB Ram, GTX MSI Gaming 1060 [6 GB] Video Card, Main Monitor 1 on left 1920x1080 Touchscreen Monitor 2 on right 1920x1080 .

Posted
38 minutes ago, sobe said:

Could someone explain to me how to do waypoints for the Viggen in the F10 map while in the jet? 

 

 

  • Like 1
  • Thanks 1

 

For work: iMac mid-2010 of 27" - Core i7 870 - 6 GB DDR3 1333 MHz - ATI HD5670 - SSD 256 GB - HDD 2 TB - macOS High Sierra

For Gaming: 34" Monitor - Ryzen 3600 - 32 GB DDR4 2400 - nVidia RTX2080 - SSD 1.25 TB - HDD 10 TB - Win10 Pro - TM HOTAS Cougar

Mobile: iPad Pro 12.9" of 256 GB

Posted

Thanks that was perfect. 

 

Trackir4 using the latest Trackir 5 software, Win10 Pro [Creator Update] updated from Win7Pro Pro 64Bit, Intel® Core™ i5-2500 3.30 GHz 6M Intel Smart Cache LGA115 , GigaByte GA-Z68XP-UD4 Intel Z68 Chipset DDR3 16GB Ram, GTX MSI Gaming 1060 [6 GB] Video Card, Main Monitor 1 on left 1920x1080 Touchscreen Monitor 2 on right 1920x1080 .

  • 3 years later...
Posted (edited)

I have this very same problem NOW. In every mission the cardridge 0 "mission defined in msn editor" waypoints go into flight computer itself nicely BUT theres ALWAYS only startup and then landingpoint. what ever i do whatever cardridge I load its always only 2 waypoints (and they are total weirdos) I will attatch pic from kneeboard datacard unloaded and loaded.

 

Unloaded (viggen running in background so there is power): 

null

image.jpeg

And cartridge loaded (+ lola + 9099 + lmal ofc) weird thing is waypoints do go into viggens comp. itself (if i press diff waypoints they are in computer, can see distances to waypoint etc and i can fly in route no prob. its just that not showing into kneeboard. Should I load some different cardridge than the default one in kneeboard? or am I doing something wrong? 

Heres picture when cartridge is loaded, why "hotstart in Air"?? (plane is on ramp coldstarted 😛 )

null

image.jpeg

Edited by Wiggo
Posted
1 hour ago, Wiggo said:

I have this very same problem NOW. In every mission ...

 

This is an unfortunate bug that managed to make it's way into the last update, and is only affecting the waypoints in the kneeboard; It has since been fixed internally and will be included in the upcoming update. The text in the "Waypoint name" field will unfortunately not be fixed in this update (the random characters), but the one after it (but it's already finished and ready).

  • Like 2
  • Thanks 1

Viggen is love. Viggen is life.

7800X3D | RTX 4070 Ti S | 64GB 6000MHz RAM |

Posted (edited)
On 4/14/2025 at 9:55 PM, MYSE1234 said:

This is an unfortunate bug that managed to make it's way into the last update, and is only affecting the waypoints in the kneeboard; It has since been fixed internally and will be included in the upcoming update. The text in the "Waypoint name" field will unfortunately not be fixed in this update (the random characters), but the one after it (but it's already finished and ready).

Yeah thanks. Found also reddit thread about this, but it was, well reddit, so couldnt be sure - now I can... 🙂 Thank you alot! As I am trialing Viggen, it was pretty crucial to know that its not me failing. Though the good part here is: Now I know how to calc that qfe ~ myself 🙂 Anyways pretty much all I need atm is those target qfe´s 🙂 But yeah thanks. heres also the reddit link..

 

Edited by Wiggo
  • Recently Browsing   0 members

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