Jump to content



Photo
- - - - -

UltraDMD Code Examples


  • Please log in to reply
3 replies to this topic

#1 Shoopity

Shoopity

    Pinball Fan

  • Members
  • PipPipPipPip
  • 691 posts
  • Location:Colorado

  • Flag: United States of America

  • Favorite Pinball: Medieval Madness

Contributor

Posted 31 August 2015 - 07:39 PM

This is the support topic for the tutorial UltraDMD Code Examples. Please post here if you have any questions or feedback.

#2 freneticamnesic

freneticamnesic

    A Faint Ghost Through the Raindrops

  • VIP
  • 3,370 posts
  • Location:Portland, OR

  • Flag: United States of America

  • Favorite Pinball: Star Trek, Black Hole, AFM, Fast Draw, Tron, AMH

  • 360 Gamer Tag: sixgunsounddd

Posted 31 August 2015 - 08:01 PM

This is very useful info, thank you



#3 allknowing2012

allknowing2012

    Pinball Fan

  • Members
  • PipPipPipPip
  • 1,948 posts
  • Location:Waterloo, ON

  • Flag: Canada

  • Favorite Pinball: bucaneer

Contributor

Posted 05 December 2015 - 01:53 AM

Shoopity, you don't really mention where DMDSceneQ is used. Do you just have code in the table script that would call it directly rather then going thru the DMDScene proc?


* I don't know everything - I just have no life *
testimageNL

 

 

 

#4 Shoopity

Shoopity

    Pinball Fan

  • Members
  • PipPipPipPip
  • 691 posts
  • Location:Colorado

  • Flag: United States of America

  • Favorite Pinball: Medieval Madness

Contributor

Posted 01 February 2016 - 03:23 AM

Sorry for the delayed response, this wasn't showing up in the "My content" section as being un-read.

 

Yes, it's just a routine written that gets called somewhere in the code (or even possibly in one of the other DMDScene routines).  It's been a while since I've worked on this, so I can't remember exactly how I implemented it in AMH (and I'm not at a computer that has VP installed), but I think in AMH I always called DMDScene throughout the game code, then the DMDScene routine actually had a bunch of if statements that determined if the scene should interrupt the current scene, queue up, or get ignored if a higher priority is playing.  But that wasn't encapsulated in the main DMDScene routine, that routine called the appropriate DMDSceneInt, DMDSceneQ, etc routines.  It is those routines that call the actual .DisplayScene00 call.