YOGEME by JaggedFel

[JaggedFel]

When you scroll through flight groups in various other panels (example orders or arrival/departure conditions), the scrolling has that 'jumping' effect instead of scrolling smoothly.

Also the main yogeme window keeps getting hidden by the map window when I try to select back to it. It forces me to either minimize the map window or move the main window to another monitor.

Fixed and fixed.

[AngeI]

Fixed and fixed.

[JaggedFel]

Okay, v1.13.3 is out for those two fixes, also added the Active Sequence tooltip.

[AngeI]

Awesome, downloaded and thank you

[JaggedFel]

Hey, can you clarify a little how region jump waypoints are supposed to be displayed? I was wanting to tidy up some waypoint and hyperspace timing issues which has a fleet of freighters go from Region 1, to 2 and then 3. But I noticed a difference between AlliED and Yogeme in how it portrays the hyperspace exit vector, so maybe I'm missing something.
...
I've also noticed the ships positions in the maps are quite different. In Yogeme its just above the backdrops position and far ahead of the hyperbuoy but in AlliED they are crowded around the hyperbuoy from their expected exit point. Whats going on here? I ask because it makes waypoint/ship direction planning difficult in Yogeme as a result right now.

Okay, so finally sat down and played with AlliEd to see what's going on. The vector lines from the exit point are all defined by the exit buoy's location to the first WP, regardless of the craft exit point, which you've already noticed.

The exit location between the player craft and NPCs are different. The player is placed 0.625 km behind the buoy along the exit vector, so when you exit you always pass through the beacon.
NPCs use the beacon location, plus the difference between the entry buoy in the previous region and the last WP in their "Hyper to Region" order. So whatever spacing you define on the entry side matches the spacing on the exit side.

Now, as for displaying in YOGEME, while I will absolutely fix the exit locations so they appear properly in the new region, I don't like how AlliEd does the trace from the exit buoy. We need the vector to determine the initial pointing, but in reality the craft isn't going to follow that path, it's going to cut in from wherever they actually are. So what I'm thinking (and I want to bounce this off a couple of you before I go do it) is that the exit vector be displayed behind the craft's exit point as a dashed line, so you will see from where the craft is coming from, but the solid line to WP1 would be from the craft itself, not the buoy, something like the mock-up below.

hyp-idea.png

I'd probably limit the dashed line to 0.5 km or so, whatever looks good.

[the_stag]

In the example above, that is for an AI craft? Since the player craft would have to go through the buoy I would guess so. In your proposal, would YOGEME be able to show the exact exit vector for all AI craft based on where they are in location to the hyper buoy in the previous sector? Because that would be awesome.

Based on what you describe and what I see in the image, I think this is a great solution. I'm certainly more interested in what @AngeI thinks than what I think, since he's invested many more hours into mission editing and creation than anyone else.

[AngeI]

@JaggedFel this looks good to me. I've in the past had trouble understanding the exit vectors for AI ships, because they don't exit in the same formation they enter when done at angles. This is an example from an old thread when I first encountered this problem: viewtopic.php?f=9&t=12802

However if you think you can accurately determine and show the exit vectors of AI ships and then use WP1 solid line to determine their directional vector when exiting (if I understand your proposal correctly), then this looks like a good solution

[JaggedFel]

Alright. I'll do some testing to see how AlliEd compares to XWA itself, especially since the exits shown in the other thread are a bit off. On one hand matching AlliEd (within reason) helps everyone who's used to it, but if I can match XWA, that's even better.

[AngeI]

Alright. I'll do some testing to see how AlliEd compares to XWA itself, especially since the exits shown in the other thread are a bit off. On one hand matching AlliEd (within reason) helps everyone who's used to it, but if I can match XWA, that's even better.

Awesome. Yeah its just weird how if you look at the pictures I posted, the formation is maintained, but the ships positions are mirrored even though they're pointing in a different direction.

[Ace Antilles]

@Jagged Fel an unusual request maybe.
Flightgroups numbers are listed starting at 1. Understandable.
But all the hook editing for various skins or FG markings etc ref the Flightgroups lines starting at 0.
Example.

Code: Select all

fg, 0, markings, 2

I'm always making rookie mistakes when setting up Mission INIs with this.

Can there maybe be a setting option that means we can list the FG from 0?
So it would say " Flight Group #0 of 49 "
Thanks

[JaggedFel]

@Jagged Fel an unusual request maybe.
Flightgroups numbers are listed starting at 1. Understandable.
But all the hook editing for various skins or FG markings etc ref the Flightgroups lines starting at 0.
Example.

Code: Select all

fg, 0, markings, 2

I'm always making rookie mistakes when setting up Mission INIs with this.

Can there maybe be a setting option that means we can list the FG from 0?
So it would say " Flight Group #0 of 49 "
Thanks

Shouldn't be too bad, can do the same with Messages.

[Ace Antilles]

Shouldn't be too bad, can do the same with Messages.

Great thanks. Whenever Jeremy lists new codes it starts at 0.

I've just been looking at your Hook Assignment tool and it is very good. I do need to try it out more.
Most of my work though has been small edits to things already inputted. So manual edits but I should use it to check stuff

[JaggedFel]

I have quite the to-do list for adding more hook compatibility once I finish working on the Waypoint updates.

[Ace Antilles]

I have quite the to-do list for adding more hook compatibility once I finish working on the Waypoint updates.

Yes I'm just trying to keep up with it myself lol
Angel has had lots of cool ideas added, and I've requested lots of hangar stuff like Droid FG colours.
Then there's a lot of Sound options that thankfully you won't need to worry with

[AngeI]

Hello, minor quibble. Would it be possible in FG goals to have 'Enable for Team' to be automatically checked by default? I keep forgetting each time I add a goal, test then realise its not enabled.

[JaggedFel]

Hello, minor quibble. Would it be possible in FG goals to have 'Enable for Team' to be automatically checked by default? I keep forgetting each time I add a goal, test then realise its not enabled.

How about leaving default unchecked (don't want XWA checking a bunch of empty goals), but if the FG Goal is modified to anything other than "none (FALSE)" then auto-check, and if modified back then auto-uncheck? You'd still be able to toggle manually of course, but that would remove the step during the initial build.

[AngeI]

How about leaving default unchecked (don't want XWA checking a bunch of empty goals), but if the FG Goal is modified to anything other than "none (FALSE)" then auto-check, and if modified back then auto-uncheck? You'd still be able to toggle manually of course, but that would remove the step during the initial build.

Sure, sounds good

[JaggedFel]

I went and posted 1.13.4 ahead of me finishing the Waypoint stuff, it's got the option to toggle 0/1-indexed for FGs from the "Overall" options page for @Ace Antilles, and it's got the auto-toggle Goal enable for @AngeI

[Ace Antilles]

I went and posted 1.13.4 ahead of me finishing the Waypoint stuff, it's got the option to toggle 0/1-indexed for FGs from the "Overall" options page for @Ace Antilles, and it's got the auto-toggle Goal enable for @AngeI

Thank you! Looks like it works. That will help my rubbish brain at times rather than add one when I should subtract etc lol
I'm also going to try using the Hook and Skin function etc as even I still can't always get my head around that

[AngeI]

I went and posted 1.13.4 ahead of me finishing the Waypoint stuff, it's got the option to toggle 0/1-indexed for FGs from the "Overall" options page for @Ace Antilles, and it's got the auto-toggle Goal enable for @AngeI

Awesome thank you!

[AngeI]

@JaggedFel I'm getting a crash on this new version. Mission I'm working on, as I switch to Region 2 on the map causes a repeatable crash:



************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at Idmr.Yogeme.MapForm.MapPaint()
at Idmr.Yogeme.MapForm.numRegion_ValueChanged(Object sender, EventArgs e)
at System.Windows.Forms.NumericUpDown.OnValueChanged(EventArgs e)
at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
at System.Windows.Forms.NumericUpDown.UpButton()
at System.Windows.Forms.UpDownBase.UpDownButtons.OnUpDown(UpDownEventArgs upevent)
at System.Windows.Forms.UpDownBase.UpDownButtons.BeginButtonPress(MouseEventArgs e)
at System.Windows.Forms.UpDownBase.UpDownButtons.OnMouseDown(MouseEventArgs e)
at System.Windows.Forms.Control.WmMouseDown(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

[JaggedFel]

@JaggedFel I'm getting a crash on this new version. Mission I'm working on, as I switch to Region 2 on the map causes a repeatable crash:

Can you send me the mission? I need to see exactly where the crash is occurring, and it's working fine with stock missions on my end.

EDIT:
Never mind, I found it. I could trigger it if SP1 wasn't checked when changing regions; a section of code for the not-yet-completed hyper exit fixes wasn't being bypassed they way I intended. 1.13.5 posted.

[AngeI]

Can you send me the mission? I need to see exactly where the crash is occurring, and it's working fine with stock missions on my end.

EDIT:
Never mind, I found it. I could trigger it if SP1 wasn't checked when changing regions; a section of code for the not-yet-completed hyper exit fixes wasn't being bypassed they way I intended. 1.13.5 posted.

That worked, thank you

[AngeI]

Hi @JaggedFel, in using the map briefing editor, am I missing something or is it possible to add the ability to 'adjust time for all following instructions' like AlliED has if you just want to shift everything down or up in the timeframe? This is a very useful feature for me I do use to make sure everything is adjusted accordingly.

Untitled.jpg

[JaggedFel]

Not currently, but I can put it on the list and add that ability.