Skip to content

Issues getting rumpus building / running #7

@mgsloan

Description

@mgsloan

Hey! Rumpus and related packages looks really cool, awesome work! After getting extra-lib-dirs and such set up to what seem to be acceptable spots, I fixed a couple type errors with this diff:

diff --git a/src/Rumpus/Main.hs b/src/Rumpus/Main.hs
index 67c38ce..8c9c803 100644
--- a/src/Rumpus/Main.hs
+++ b/src/Rumpus/Main.hs
@@ -64,7 +64,7 @@ initializeECS ghc pd vrPal = do

 rumpusMain :: IO ()
 rumpusMain = withRumpusGHC $ \ghc -> withPd $ \pd -> do
-    vrPal <- initVRPal "Rumpus" [UseOpenVR]
+    vrPal <- initVRPal "Rumpus"

     --singleThreadedLoop ghc pd vrPal
     multiThreadedLoop ghc pd vrPal
diff --git a/src/Rumpus/Systems/Render.hs b/src/Rumpus/Systems/Render.hs
index ead1d1d..5f6ae1c 100644
--- a/src/Rumpus/Systems/Render.hs
+++ b/src/Rumpus/Systems/Render.hs
@@ -102,7 +102,7 @@ tickRenderSystem headM44 = do

     -- Render the scene
     vrPal  <- viewSystem sysControls ctsVRPal
-    renderWith vrPal headM44 $ \projM44 viewM44 -> do
+    renderWith vrPal headM44 $ \projM44 viewM44 _ _ -> do
         glClear (GL_COLOR_BUFFER_BIT .|. GL_DEPTH_BUFFER_BIT)
         let projViewM44 = projM44 !*! viewM44
         renderEntities     projViewM44 shapeCounts

Not sure why this is needed, I have the latest version of vr-pal. Maybe it'd be better to use git submodules / SHAs in the stack.yaml? I realize it's less convenient, but seems like we have a version mismatch here.

Anyway, with that patch and ghci I get the following output:

*Main> main
No redirect found in C:\Users\Sirius.Orangetan\Documents\Rumpus\redirect.txt
Using rumpus root: pristine
Loading scene: pristine\Lobby
SubHalive recompiling: ("pristine\\Lobby\\Platform.hs","start")
SubHalive recompiling: ("pristine\\Lobby\\Stars.hs","start")
SubHalive recompiling: ("pristine\\Lobby\\DoorMaker.hs","start")
Segmentation fault

With the built executable, I get dll loading issues. I tried copying all the relevant dlls right next to the exe, and got passed those via that approach, but now it immediately exits, printing a newline. Do I need to have the Vive ready to go? Unfortunately at the moment I can only connect either the Vive or monitor at once, and the Vive software really doesn't seem to be designed for that!

It's been something like 9 or 10 years since I developed on windows, so I'm pretty rusty at this stuff.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions