Home › Games › EmptyEpsilon
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Quick Links
Categories
- 530 All Categories
- 4 News
- 3 News and more
- 50 Rec Room
- 14 General
- 5 Off-Topic
- 6 Custom & Commercial Simulators
- 6 TV Shows, Movies, & Books
- 18 Forum & Website
- 321 Games
- 37 Artemis SBS
- 210 EmptyEpsilon
- 8 Quintet
- 11 Sigma Tau
- 8 Space Nerds in Space
- 9 Starship Horizons
- 33 Other Games
- 14 Software
- 8 Mods & Models
- 4 Helper Applications
- 1 WINE & Emulation
- 10 Hardware
- 6 Computers, Tablets, Screens, & Networking
- 4 Custom Controllers
- 18 Enhancing Your Games
- 11 Bridge Construction
- 2 Uniforms & Costumes
- 1 Props
- 3 Graphics & User Interfaces
- 33 Events
- 29 Conventions & Events
- 2 Meetups
- 2 Event Planning
- 5 Crews & Groups
- 5 Looking for Crew
- Groups Looking for Groups
- 1 Mission Reports
- 1 Mission Log
Comments
I was rather thinking about radar blips in the style of EVE Online :
I've tried to reduce it and make it black&white, to apply it to the Ktiltian Scout template. Sadly, I kinda suck at art and things went worse than expected :
(I've converted to grayscale on GIMP, then enhanced sharpness. Maybe I need to fiddle with some of the parameters to have)
I tried to fire up EE anyways to see how it looked :
An important point would be art consistency, and not to have a patchwork of vessels of different styles.
When the view is switched to Helm only, the wobble stops. Reducing the manoeuvrability power will also fix the wobble.
Also want to remove a bunch of duplicate code between the stations and ships.
We had a little game this night with 3 friends to try the new build this is our feedback.
Globally we really liked it and we are impressed by the evolution of the game. We saw that the warp drive had some tweaks, now we can "cruise" for long distance like in star trek. Still, there is a speed cap at 150km/min. Is it a limitation from the game engin or a "personal" choice ? Thus going into warp 3.0 or 4.0 or pushing the warp core at 200% and warp 2.0 dosent change anything.
We had a few suggestion tho :
-Would it be possible to have a zoom in the science view ?
-In the relay view, would it be possible to have a "jump view to coordinates". In case of a really big map you sometime want to jump the view somewhere on the map.
-Sometimes the heat indicator shows that it should be decreasing but it still going up. Exemple : Going warp 2.0 and the warp core at 150%~175% with loots of coolant the heat arrow show its should decrease but the heat actually goes up.
-I saw in the basic scenario that they are some astéroïdes but I could not find it in the GM "create" menu.
-Could we have asteroids from different sizes ?
We find the GM menu well done and easy to manage but there is a few little gizmo that we think would enrich the GM and the players expérience.
-The possibility to "add text" to objects and when the science scan it he would see the text. (and the possibility to scan astéroïde and bases)
-The possibility for the GM to give reputation and energy to the players.
-The possibility to "save the map" in the gm view. Sort of a Map creator.
Sorry if there is some doublons from previous post.
And thanks for the great job and we might tip the cookie jar shortly
By the way @daid I'm loving those Yellow/Red alert overlays. Do you have enough for the new Frigate models you wanted now?
-Would it be possible to have a zoom in the science view ?
With the new radar implementation I did a while back to fix some issues I can think of a few ways on how to do this.
-In the relay view, would it be possible to have a "jump view to coordinates". In case of a really big map you sometime want to jump the view somewhere on the map.
How big of a map are you playing on? A jump-to-sector could be useful I guess. Have to see how to work this out for touch-screen play.
-Sometimes the heat indicator shows that it should be decreasing but it still going up. Exemple : Going warp 2.0 and the warp core at 150%~175% with loots of coolant the heat arrow show its should decrease but the heat actually goes up.
Current heat indicator arrow only accounts for power/coolant levels, not for extra heat generated from engines/beamweapons/etc...
-I saw in the basic scenario that they are some astéroïdes but I could not find it in the GM "create" menu.
Yes, these are not creatable from the GM screen yet. There are more objects that are currently scripts only.
-Could we have asteroids from different sizes ?
Could look into that. Should not be too complex.
-The possibility to "add text" to objects and when the science scan it he would see the text. (and the possibility to scan astéroïde and bases)
Instead of astroids there are "artifacts" that can be scanned, and can be made to look like anything. But only from scripts right now. Scripts can also apply descriptions on objects that science can see.
-The possibility for the GM to give reputation and energy to the players.
Good point.
-The possibility to "save the map" in the gm view. Sort of a Map creator.
F5 copies the current map to the clipboard so you can save it to a scenario script. This is not a full "save", but a map creator feature. As it does not save every property of ships right now.
https://github.com/Wrongtown/EmptyEpsilon
With "new pull request".
Also note that you still have a merge conflict unresolved in your fork:
https://github.com/Wrongtown/EmptyEpsilon/blob/master/scripts/scenario_03_edgeofspace.lua#L550
(Nothing I cannot do/fix myself. As I can also create a pull request from your fork. But you expressed the willingness to learn. So I hope you appreciate the comments)
Meanwhile I may have finally got that Pull Request in order, please let me know if I've missed anything. I definitely appreciate the opportunity to learn more and thereby be more useful!
On that note, I've been trying to investigate how to play sounds at certain points in a .lua script, I found this documentation but I keep getting an error stating that I'm attempting to index a nil value (global 'audio') so I'm guessing I'm missing where I go about defining "audio" as an entity earlier in the script?
I havent check out the scrips yep, I'm not so good with programmation so I fear the moment I have to "creatobject" and stuffs like that. Is there a technical difficulties to just have a "add asteroids" in the create menu in the gm screen ?
I'm gona try that F5 feature.
For the size we tested ou some warp speed up to "jj26" so yeah quite far. The goal is to have a small exploration scénario where the players must travel à big distance analyse stuffs, investigate, doing a bit of roleplay (going to the shipwreck, analyzing samples, ...) then come back. So not just fight scénario.
So having some "customizable" astéroïdes, debris, shipwreck would be fun. And by customizable i mean adding a bit of text and to possibility to scan it.
Adding astroids to the GM menu should be easy.
See: https://github.com/daid/EmptyEpsilon/blob/master/src/screens/gameMasterScreen.cpp#L476
Some result of the shield rework I'm doing:
Only did stations right now. And I have bugs on the "which shield is hit" detection. Can be done with the Artifact object. Example:
a = Artifact():setPosition(1000, 1000) a:setModel("shield_generator") --Any model from the model_data.lua a:setDescription("An odd object in space...") a:setScanningParameters(2, 2) -- Set the scanning requirements to 2 sets of 2 bars(Note, untested. Not sure if scanning already works properly)
This file contains all the functions that can be called on objects. It's by no means a guide, but it is generated from the code so it will contain all functions.
For general Lua, you can check:
http://www.lua.org/manual/5.3/
Note that the io, os, file and debug functions are not available for security reasons.
1) Tutorial instructions (alternatively some method of popping up dialogue on any given station could work, but seems like this could interfere with the user trying to follow those instructions).
2) The possibility of sending Comms messages which include an option to play a recording. I've seen this used to decent effect in Artemis SBS missions.
I do think that both of these cases could bloat the size of the core, so would probably be best to package such missions as an optional package.
Currently, player ships should only be fitted with 1 or 2 shields. As there are no engineering systems for more then 2. (Rear system will control all the other shields as well)
I've also updated the script functions a bit, instead of using "setTemplate" for stations and "setShipTemplate" for ships, now both need to use "setTemplate". "setShipTemplate" is still available, but will be removed at some point. (just don't want to break all custom changes right now)
It still misses script functions to properly query and modify all the shields. But the basic new shield implementation should work fine ingame now.
I'd say that the scripting could do with a simple playSound for each station and a location based (simple X, Y and a "size" (linear falloff in volume)). The location based should be handled by the server (and thus heard by all players).
On a completely different note; holyshit, where did all the new people came from. Didn't check this page for some time, and all of the sudden there are a gazillion people working on this. Awesome!
@nallath sounds good to me. Most of the time you'd probably want to play through Main Screen, but the Tutorial example I gave before might be good for the new player to hear it directly through their station. That way a crew of newbies could all be running through their station tutorial in parallel rather than one at a time. Mind you I guess they could just run a Main Screen + Station and they'll hear it anyway.
Looks to be a SeriousProton problem. Seems to be due to a newer commit. Possibly in src/scriptOnterfaceMagic.h
My Build script should now log and upload failures to http://brigdesim.net/build/emptyepsilon. Files should have the .FAIL extension.
Here's the latest fail log http://bridgesim.net/builds/emptyepsilon/EmptyEpsilon-EXE_20160108-1125_e39e589.FAIL It includes the SP & EE commit rev numbers.
Compiler errors in template code are always difficult to read. But it comes down to the fact that it cannot find a method to convert a list of parameters to a script function to a C++ list.