Geometry Nodes: Cascading / Dependent Menus

Problem: Menu sockets are static.

You can make a dropdown, but you cannot change its items based on another menu.

This makes multi-level selection awkward and cluttered.

Example

Generic use case:

• Category → Item

  • “Vehicle Type” → “Car / Bike / Boat”

  • Then second menu should update:

    • Car → “Sedan / SUV / Truck”

    • Bike → “Road / MTB / BMX”

    • Boat → “Sail / Motor / Cargo”

Right now, all options must exist at once, or be split across multiple menus.

Current Workarounds:

1. Multiple menus + switch logic

• One menu per category
• Only one is actually used
• UI becomes cluttered

2. Separate node groups per category

• Cleaner UI
• Harder to maintain and reuse

3. Index-based systems

• Works internally
• Not user-friendly

None of these scale well.

Proposal:

Add support for cascading (dependent) menus:

• A menu can define its items based on another menu’s selection
• Second-level menu updates dynamically
• Only relevant options are shown

Expected Behavior:

• Menu A defines a category
• Menu B reads Menu A and updates its item list